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.
1. Create a EE 6 web application with GlassFish 3.1.1 target 2. Add JSTL from the Library Manager to the project libraries 3. Use JSTL in index.jsp, e.g. <c:out value="here"/> 4. Deploy the application 5. Clean and build The following error appears in the output window: init: undeploy-clean: Undeploying ... Initializing... deps-clean: do-clean: Deleting directory C:\Users\pjiricka\Documents\NetBeansProjects\WebApplication5\build C:\Users\pjiricka\Documents\NetBeansProjects\WebApplication5\nbproject\build-impl.xml:1054: Unable to delete file C:\Users\pjiricka\Documents\NetBeansProjects\WebApplication5\build\web\WEB-INF\lib\jstl.jar BUILD FAILED (total time: 2 seconds)
Different steps to reproduce: 1. Create a EE 6 web application with GlassFish 3.1.1 target 2. Add JSTL from the Library Manager to the project libraries 3. Deploy the application 4. Shut down GlassFish and NetBeans 5. Start GlassFish from the command line and access the application URL through a web browser 6. In the command prompt, switch to the project root directory and run 'ant clean' = > This fails with the same error as above. And also: 1. Create a EE 6 web application with GlassFish 3.1.1 target 2. Add JSTL from the Library Manager to the project libraries 3. Deploy the application 4. Shut down GlassFish from the Services window 5. Clean and build the project => Now the clean succeeds. These scenarios show that the problem is on the side of the GlassFish runtime, which holds a lock on the jar file. Vince, could you please discuss this with whoever is responsible for this area on the runtime side? Thanks.
(In reply to comment #1) > Different steps to reproduce: > > 1. Create a EE 6 web application with GlassFish 3.1.1 target > 2. Add JSTL from the Library Manager to the project libraries > 3. Deploy the application > 4. Shut down GlassFish and NetBeans > 5. Start GlassFish from the command line and access the application URL through > a web browser > 6. In the command prompt, switch to the project root directory and run 'ant > clean' > = > This fails with the same error as above. Actually, this should fail... since you haven't undeployed the app and the server is still live... > And also: > > 1. Create a EE 6 web application with GlassFish 3.1.1 target > 2. Add JSTL from the Library Manager to the project libraries > 3. Deploy the application > 4. Shut down GlassFish from the Services window > 5. Clean and build the project > => Now the clean succeeds. > > These scenarios show that the problem is on the side of the GlassFish runtime, > which holds a lock on the jar file. Vince, could you please discuss this with > whoever is responsible for this area on the runtime side? Thanks. I will raise the issue again. There isn't a plugin change that will address this... so this issue is invalid (using a strict definition). I am going to drop it to p3 and leave it open to keep it monitored.
Why are we packaging jstl.jar in the app when it targets glassfish? $ find . -name '*jstl*.jar' ./glassfish/modules/javax.servlet.jsp.jstl.jar ./glassfish/modules/jstl-connector.jar ./glassfish/modules/jstl-impl.jar
filed gf issue http://java.net/jira/browse/GLASSFISH-17339
moving to p4. this issue should not be counted in the stop ship criteria for NB... since there is nothing that folks in the NB team can do about it...
Thanks a lot for filing the GlassFish bug; I agree with downgrading this to P4. Regarding the question about packaging JSTL, I think the reason is that there is no API that would allow the plugin to specify whether the server contains JSTL.
*** Bug 202724 has been marked as a duplicate of this bug. ***
*** Bug 204320 has been marked as a duplicate of this bug. ***
This bug is supposedly fixed on the GlassFish side in promoted build 13: http://dlc.sun.com.edgesuite.net/glassfish/3.1.2/promoted/ Can someone who has a Windows machine please check whether using the new GF build fixes this? Thanks.
I understand that this is a GF issue that shows up in a development environment. Do I took the testcase from issue and re-tested it under NetBeans. This time I get a different error where it seems that the servlet API cannot be found. I installed glassfish-3.1.2-b13-windows-ml.exe and registered it with NetBeans. init: undeploy-clean: deps-clean: do-clean: Deleting directory C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build check-clean: clean: init: deps-module-jar: deps-ear-jar: deps-jar: Created dir: C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web\WEB-INF\classes Copying 1 file to C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web library-inclusion-in-archive: Copying 1 file to C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web\WEB-INF\lib Copying 1 file to C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web\WEB-INF\lib Copying 1 file to C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web\WEB-INF\lib library-inclusion-in-manifest: Created dir: C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\empty Compiling 2 source files to C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\build\web\WEB-INF\classes C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:35: package javax.servlet does not exist import javax.servlet.*; C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:36: package javax.servlet.annotation does not exist import javax.servlet.annotation.WebServlet; C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:37: package javax.servlet.http does not exist import javax.servlet.http.*; C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:47: cannot find symbol symbol: class HttpServlet extends HttpServlet { C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:45: cannot find symbol symbol: class WebServlet @WebServlet(name="Servlet", urlPatterns={"/servlet"}) C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:58: cannot find symbol symbol : class HttpServletRequest location: class servlet.stateless.Servlet2Stateless public void service(HttpServletRequest req, HttpServletResponse resp) C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:58: cannot find symbol symbol : class HttpServletResponse location: class servlet.stateless.Servlet2Stateless public void service(HttpServletRequest req, HttpServletResponse resp) C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:59: cannot find symbol symbol : class ServletException location: class servlet.stateless.Servlet2Stateless throws ServletException, IOException { C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:89: cannot find symbol symbol : class ServletException location: class servlet.stateless.Servlet2Stateless throw new ServletException(ex); C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\src\java\servlet\stateless\Servlet2Stateless.java:57: method does not override or implement a method from a supertype @Override 10 errors C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\nbproject\build-impl.xml:543: The following error occurred while executing this line: C:\bt\java\GlassFish\V3\issues\_closed\GlassFishDoesNotReleaseJarFile\ServletStateless\nbproject\build-impl.xml:297: Compile failed; see the compiler error output for details. BUILD FAILED (total time: 3 seconds)
It seems to be fixed in GlassFish 3.1.2 build 13. Tested on Windows XP.
I must say this still does not work for me using an application that contains a web service and packages a separate copy of Jersey. I am using GF 3.1.2 final, NetBeans build from March 21st (Build EaselCSS-144-on-20120321) and: Java: 1.7.0_02; Java HotSpot(TM) Client VM 22.0-b10 System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb) The output window says: ant -f C:\\easel_demo\\SampleDBrest\\build.xml -DforceRedeploy=false clean init: undeploy-clean: Undeploying ... deps-clean: do-clean: Deleting directory C:\easel_demo\SampleDBrest\build C:\easel_demo\SampleDBrest\nbproject\build-impl.xml:1092: Unable to delete file C:\easel_demo\SampleDBrest\build\web\WEB-INF\lib\jersey-gf-server.jar BUILD FAILED (total time: 2 seconds)
The workaround is to shut down GlassFish, after that the Clean operation succeeds.
I have had seemingly random failures as well, but failed to reproduce them. At the same time, I found one case in my app that reproduces, but that seems to be caused by a web framework not GlassFish. See https://issues.apache.org/jira/browse/WICKET-4458 After all I have to say that NetBeans integration is quite good and ahead of other IDE's "disintegrated" approach. Only due to this integration do I actually get into the finer details while otherwise I would have to spend more time getting incompatible plugins to work. I have just seen this with Java Web Start where NetBeans again does it out of the box where Eclipse is a 100% failure. Now I am spending time to hand-code a build script for that environment, basically reverse-engineering what NetBeans provides so it fits within one of the myriad of "standard" corporate "build environments". Why not just take a NetBeans-generated build script, extend it if necessary and run it on a build server?
(In reply to comment #12) > I must say this still does not work for me using an application that contains a > web service and packages a separate copy of Jersey. I am using GF 3.1.2 final, > NetBeans build from March 21st (Build EaselCSS-144-on-20120321) and: > Java: 1.7.0_02; Java HotSpot(TM) Client VM 22.0-b10 > System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb) > > The output window says: > > ant -f C:\\easel_demo\\SampleDBrest\\build.xml -DforceRedeploy=false clean > init: > undeploy-clean: > Undeploying ... > deps-clean: > do-clean: > Deleting directory C:\easel_demo\SampleDBrest\build > C:\easel_demo\SampleDBrest\nbproject\build-impl.xml:1092: Unable to delete file > C:\easel_demo\SampleDBrest\build\web\WEB-INF\lib\jersey-gf-server.jar > BUILD FAILED (total time: 2 seconds) It looks like the root cause of http://java.net/jira/browse/GLASSFISH-17339 was a bug in the JSTL library or one of its dependencies. That may be the root cause of what you are seeing in this case (since you are talking about using a different library).
I'll check this again in next release cycle.