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.
I noticed that when building netbeans, some modules go into nbbuild/netbeans/extra instead of their correct location. This causes problems for example when compiling visualweb (see issue #106191). I'll include an example log. Here is the final structure that I get when building web/servletjspapi: nbbuild/netbeans/ |-- extra | |-- config | | `-- Modules | | `-- org-netbeans-modules-servletjspapi.xml | |-- modules | | |-- ext | | | `-- servlet2.5-jsp2.1-api.jar | | `-- org-netbeans-modules-servletjspapi.jar | `-- update_tracking | `-- org-netbeans-modules-servletjspapi.xml |-- moduleCluster.properties `-- module_tracking.xml 6 directories, 6 files This is produced using building just web/servletjspapi but the same result is get building all clusters needed for visualweb etc. This is just an example, there are more modules being installed the same way into extra directory. I'll attach log from the build process.
Created attachment 44011 [details] ant -d -f web/servletjspapi/build.xml build log
Works for me. Not sure what could be wrong on your machine. Please make sure you have complete and up-to-date sources with no local modifications. Your nbbuild/cluster.properties should list web/servletjspapi under nb.cluster.j2ee. The problem in the log: default.init: Setting project property: module.name -> web/servletjspapi Setting project property: cluster.dir.fallback -> extra [setcluster] No cluster list with this module: web/servletjspapi was found. Using default cluster location: extra [setcluster] Property: cluster.dir will be set to extra Setting project property: cluster.dir -> extra
*** Issue 106191 has been marked as a duplicate of this issue. ***
Sorry, the problem was on my part. Petr Pišl helped me to solve it.
frodfrog, one more comment based on the attached build log. Current build environment requires JDK 5. The log reports it found JDK 6. Please be considerate when setting dependency between linux packages. There should be no code requiring compilation by JDK 6 in NetBeans. That's because 5 is still pretty popular JDK. JDK 5 Update 11 is enough to compile&run NetBeans 6.0, while when you would have compiled the NetBeans build with JDK 6, then nothing is assured for people who want to stay with JDK 5 in your linux distribution.
Thanks for your comment. That output was created running compilation of just the single module from console where I have JDK 1.6 as the default but the ebuild is restricted to =jdk-1.5 so nb is always built using JDK 1.5. Even if it would be built with 1.6, it would be built as 1.5 source and target (unless these attributes are missing in some files which I faced with one file in nb 5.5) so if not counting the differences between what is available in each JDK (like jsr223) the result should be close to same, ie 1.5 bytecode. So I suppose in this case the dep in the ebuild could be >=jdk-1.5 though I use =jdk-1.5 to be safe :-)