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.
<nbdeploy forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" debugmode="false"/> Sometime fails, sometimes doesn't.
Not really sure what you're talking about; need a real description in English of what you did and what happened. I am guessing you are doing something with web app projects? Unclear, should be closed as INVALID unless more details are forthcoming. BTW, if you don't know which component to file a bug under - 'nbbuild' was definitely not right - please just use 'ide' and it will get reassigned.
When you click redeploy on a webapp project, it fails and says there was an error trying to execute line 236 in build-impl.xml. Usually, after this error occurs, the webapp has successfully deployed/redeployed before. When this occurs, the whole redeploy process has appearently succeeded but displays an error.
Workaround for this is to go to runtime tab and undeploy the web module.
Appearently, this only occurs if you install a dev build without deleting .netbeans/dev. That is to say, you install a newer dev build after having already installed a dev build. For example: Using Q-Build 200409100847 after having used Q-Build 200408271257. So, this may be a non-issue since 4.0 Final will use .netbeans/4.0
The cause of this issue is, that the IDE sometimes fails to detect the need to run undeploy before deploying a web application. Fixed two cases when deployment failed. Filed a new issue 50554 for case when deployment failed after server port change. Currently we do not plan to fix a case, when user wants to deploy web application to an already used context path to which was previously deployed not using IDE (this includes also predeployed webapps "/", "/admin", "/balancer"). Users have to manually undeploy the old web application for deployment to be successful. Exception from this scenario is when deploying a not yet deployed application, which should succeed. Commit log: 1) this fixes the case when IDE tries to deploy a not yet deployed application to a context path which is already in use on the server Checking in src/org/netbeans/modules/j2ee/deployment/impl/TargetServer.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/TargetServer.java,v <-- TargetServer.java new revision: 1.36; previous revision: 1.35 done 2) this fixes the case when deploying to ROOT context path Checking in src/org/netbeans/modules/tomcat5/TomcatModule.java; /cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/TomcatModule.java,v <-- TomcatModule.java new revision: 1.8; previous revision: 1.7 done Processing log script arguments... More commits to come... Checking in src/org/netbeans/modules/tomcat5/ide/TMIDResolver.java; /cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/ide/TMIDResolver.java,v <-- TMIDResolver.java new revision: 1.3; previous revision: 1.2 done
v