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.
The JSP compile option on a web project is not handled in a cross-platform manner, so that when configured on one platform (OSX) the build will fail when run on a different platform that uses different syntax for a classpath. Details: Project was configured on an OSX system, so the nblibraries.properties file was built using the colon (:) between each file path. For most classpath properties in that file, this syntax works fine because the property value ends up being processed by an ant task that accepts either colon (:) or semi-colon (;) as the delimiter character in a classpath. However, the -sysClasspath parameter to the JSP compiler apparently requires the correct syntax for the current platform, so when run on a Windows OS only the semi-colon is accepted as the delimiter. As a result, the project build fails when the classpath in the nblibraries.properties file uses a colon. The actual error reported is a java.io.FileNotFoundException, but the file name reported with the exception is the entire -sysClasspath parameter. Standard web project with project-specific library. Project was updated from NB 6.9.1 to NB 7.0.
Not sure how much doable. When it should be checked/updated - before every build action? CCing David, he will be able to tell if it's wanted at all/possible or not.
<java> task is used to execute JSP compilation and it is executed with sysClasspath parameter in the format it is stored in properties file. I think it should be possible to add some Ant task call to "compile-jsps" and "-do-compile-single-jsp" targets which would ensure correct platform specific encoding of classpath (turn string path into some Ant path property and then dump property back to string using for example ${toString:pathreference}).
Just encountered the same issue as we develop under Linux but a CI server just introduced is running under Windows. The following change to the compile-jsps target (following David's suggestion) in build.xml did the trick for us: old: <java classname="org.netbeans.modules.web.project.ant.JspC" failonerror="true" fork="true"> ... <arg value="-sysClasspath ${libs.jsp-compilation-syscp.classpath}:${javac.classpath}"/> ... </java> new: <path id="sys.class.path"> <pathelement path="${libs.jsp-compilation-syscp.classpath}"/> <pathelement path="${javac.classpath}"/> </path> <java classname="org.netbeans.modules.web.project.ant.JspC" failonerror="true" fork="true"> ... <arg value="-sysClasspath ${toString:sys.class.path}"/> ... </java>
Another less intrusive workaround here: http://stackoverflow.com/questions/19817905/netbeans-fails-to-compile-jsp-in-projects-created-on-diferent-os/19817906#19817906
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss