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.
[20040518] To reproduce: 1) create a J2SE library project e.g. libprj 2) create a package and inside a class with a static method returning a string. 3) create a new Web project 4) add the libprj project into the webproject compilation classpath 5) create a JSP page rendering value of the static method from the libprj 5) build the web project 6) make a change in the static class e.g. return a different string 7) build the main web project => the JSP page still uses the old class version. The library built in the libprj is correctly copied into the ${webproject}/build/web/WEB-INF/lib, but the webmodule is not reloaded or redeployed so the webapp classloader still sees the old class version.
The problem is even more general and serious. The webmodule is not reloaded even if you change a class inside the project or add a new library into. After running the project everything is properly updated in ${webproject_home}/build/web/*, but the webmodule is not reloaded / redeployed. So the only workaround is to perform the "Redeploy Project" action.
Thanks for catching this. There were problems on both sides - web module did not list its files correctly (listed files from sources folder and with wrong relative paths) and j2eeserver did its own enumeration of files -- also incorrectly (also with wrong relative paths). Because of the second problem I wonder how this could have worked in 3.6 :-( It is fixed now.
verified in #20040707