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.

Bug 99843 - Can't clean and build while packaged Tomcat container is running.
Summary: Can't clean and build while packaged Tomcat container is running.
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-03 15:44 UTC by hornbacher
Modified: 2007-08-13 15:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hornbacher 2007-04-03 15:44:49 UTC
When the packaged tomcat (version 5.5) container is running, the clean and build
command returns an error and will not create a new build.  But if I shut down
tomcat, it cleans and builds correctly.  I am using netbeans 5.5.
Comment 1 Jiri Prox 2007-04-03 17:19:10 UTC
Can you attach the error message, please? What type of project did you use?
Comment 2 Jiri Prox 2007-04-03 18:03:07 UTC
From reporter:

Error Message:

init:
deps-clean:
do-clean:
Deleting 8 files from C:\Develop\LIMSOutput\build\web\WEB-INF\lib
Deleting directory C:\Develop\LIMSOutput\build
C:\Develop\LIMSOutput\nbproject\build-impl.xml:703: Unable to delete file
C:\Develop\LIMSOutput\build\web\WEB-INF\lib\jsf-impl.jar
BUILD FAILED (total time: 2 seconds)

Project Type:
Java Server Faces


Reassigning to Tomcatint for evaluation
Comment 3 Sherold Dev 2007-08-13 15:21:03 UTC
Probably the only way how to fix this issue would be to undeploy the application before cleaning the project. This fix
would be rather controversial and would slow down clean & build action, currently we do not plan to fix this -> marking
the issue as WONTFIX.

Note that there is a couple of work-arounds which you can use. You can stop or undeploy the application manually from
the Services window. Another work-around would be to add antiResourceLocking="true" to your context.xml file, see
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html.