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.
[20040111] When you deploy a webmodule containing JSPs, Servlets and other resources and then delete some of them in the IDE and redeploy the WM, the deleted resources remains deployed.
this is more likely to be caused by a problem in j2eeserver then web module, I'll take a look at this
I was not sure about that so thank you for evaluating that.
Just a note: This is no longer problem of tomcat deployment since the semantic has been changed. The deployed webmodule is not copied in a form of a war file to the server. Instead of that, the Context element in the tomcat's context definition file contains docBase property, which points in the webmodule directory directly.
So this is still problem for file-copy incremental deployment unless we do cleanup at the target of the copying. The code for clean up is disable pending new API's because there are files put in the destination directory by the plugin or appserver. This is on my deployment loosends which must be solved in promoD.
Only affect plugins with file-copy incremental deploy, none so far. To be reevaluated or resolved in promo-D.
With 4.0 CDP buildsystem, incremental deploy is still kind of in-place deployment with build output (or staging) area as the in-place directory. So removal a jsp or servlet should be reflected by change in descriptor and causing app reload. Only removal of a regular java class would not be detected, but this should not cause any problem in execution of the app. I am closing this bug as fixed.