This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I have an enterprise project of type org.netbeans.modules.j2ee.earproject which I am deploying to glassfish v3 via commandline ant, but the ant deployment step doesn't work and the problem is here in ant-deploy.xml: <get src="${gfv3.url}/__asadmin/deploy?path=${full.deploy.ant.archive}${deploy.context.root.argument}?force=true?name=${ant.project.name}" It is getting an authorisation exception, and no surprise there because it isn't passing the basic authentication username and password, which already exist in some java properties gfv3.username and gfv3.password. So if I hand modify it to be as follows, it works because it then is authenticating properly: <get username="${gfv3.username}" password="${gfv3.password}" src="${gfv3.url}/__asadmin/deploy?path=${full.deploy.ant.archive}${deploy.context.root.argument}?force=true?name=${ant.project.name}" It seems wrong that netbeans would create an ant-deploy.xml without those.
It looks like I should be able hack around the problem by updating this jar from the netbeans install, changing the contents of ant-deploy.xml: enterprise/modules/org-netbeans-modules-glassfish-javaee.jar The file within the jar is: org/netbeans/modules/glassfish/javaee/ant-deploy.xml
A slightly different url issue, but on the very same line: <get username="${gfv3.username}" password="${gfv3.password}" src="${gfv3.url}/__asadmin/deploy?path=${full.deploy.ant.archive}${deploy.context.root.argument}?force=true?name=${ant.project.name}" Note that it has ?....?force=true?name=.... Surely that should be &...&force=true&name=....
thanks. i will look into it.
http://hg.netbeans.org/web-main/rev/f83a064c6efb
the changes are in main-golden http://hg.netbeans.org/main-golden/rev/f83a064c6efb http://hg.netbeans.org/main-golden/rev/29a7cda97f53