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.
Sources: http://download.netbeans.org/netbeans/6.5/rc/zip/netbeans-6.5rc1-200810171318-src.zip Build command: GENTOO_VM="sun-jdk-1.5" ANT_TASKS="ant-nodeps" ant -Dstop.when.broken.modules=true -Dbuild.compiler.deprecation=false -Dnb.clusters.list=nb.cluster.platform,nb.cluster.apisupport,nb.cluster.cnd,nb.cluster.groovy,nb.cluster.gsf,nb.cluster.harness,nb.cluster.ide,nb.cluster.identity,nb.cluster.j2ee,nb.cluster.java,nb.cluster.mobility,nb.cluster.nb,nb.cluster.php,nb.cluster.profiler,nb.cluster.ruby,nb.cluster.soa,nb.cluster.webcommon,nb.cluster.websvccommon,nb.cluster.xml -f nbbuild/build.xml build-nozip Build output: build-init: Trying to override old definition of task downloadbinaries [parseprojectxml] Distilling /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build/public-package-jars/org-netbeans-modules-j2ee-sun-ddui.jar from [/home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/netbeans/enterprise5/modules/org-netbeans-modules-j2ee-sun-ddui.jar] [nbmerge] Failed to build target: all-j2ee.sun.appsrv81 BUILD FAILED /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:720: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:715: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:750: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:733: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:715: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/build.xml:761: The following error occurred while executing this line: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/templates/projectized.xml:93: No such classpath entry: /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/netbeans/nb6.5/modules/org-netbeans-modules-reglib.jar File /home/fordfrog/gentoo/tmp/netbeans-6.5_rc1/nbbuild/netbeans/nb6.5/modules/org-netbeans-modules-reglib.jar really does not exist.
Just a little clarification, nbbuild/netbeans/nb6.5 directory does not exist at all, nbbuild/netbeans/nb.cluster.nb.built file does not exist either.
For now I added nb.cluster.nb in nb.cluster.j2ee.depends= in nbbuild/cluster.properties which makes the compilation succeed.
It is illegal for a module in enterprise cluster to have a dependency on a module in nb cluster. The reglib module would need to be pushed down into e.g. the ide cluster. IMHO this needs to be corrected for NB 6.5.
see http://hg.netbeans.org/main/rev/6ff64288ddf6 and http://hg.netbeans.org/main/rev/098872f0ea22 I asked Nitya to do these commits, so I will accept the blame for this issue... she is just the piano player. http://en.wikipedia.org/wiki/Don%27t_Shoot_Me_I%27m_Only_the_Piano_Player
more info: I followed the instruction #1 on this page http://www.netbeans.org/community/guidelines/commit.html on a recently pulled release65 clone. it builds clean. the commit-validation runs into trouble, but those failures do not appear to be related to reglib and/or appsrv81. Adding Ludo, since he is the tooling architect for GF and this is an architectural issue.
We first asked GF to provide use cases/scenario for using registration (reglib) from j2ee.sun.appsrv81. It should be done before moving reglib to ide cluster.
I think at this stage of the game, the best is to revert our change, and work with the Nb registration page to better show that when registering the NetBeans IDE you can also register either the GlassFish v2 or GlassFish v3 prelude app servers that are either bundled in the IDE (so 100% part of the IDE but with a different registration info) or used by the IDE if this IDE did not bundle them. This work can be done outside the IDE on the registration page.
fordfrog: have you tried changing the definition of the nb.clusters.list, to have nb.cluster.nb precede nb.cluster.j2ee? Since the "regular build" has been working for over 9 days, I have to assume there is a way to alter the way you invoke ant to also be successful... without altering the content of any of the files in nbbuild. (I am assuming that the build command is in a script that is not pulled from the NB hg repository...)
No, I did not try that as I did not expected that would have some effect on the build order as I thought the order is determined by the dependencies and not by the order of clusters in the list, but I can try to move the 'nb' cluster to the first position and see whether it will work.
I will revert the commits that resolved issue 149148 for the v2 integration.
Also see issue #150512 that has just been fixed.
very nice:-)
Shifting 'nb' cluster to the beginning of the list makes the compilation work.
changes in trunk... http://hg.netbeans.org/main/rev/4e90c50e9457 and http://hg.netbeans.org/main/rev/3051c94c53b4
fordfrog: please verify that you can build the trunk, using your build command. Once this is verified, I can commit similar changes to the release65 repository.
How can I get the trunk? I get 403 Forbidden on http://hg.netbeans.org/.
you are not alone. hg is dead for everyone currently...
jglick: would you take a moment to confirm that rollback in the trunk was fine? I would like to get this issue converted to verified, so I can push into the release65 repository.
I just verified that the error does not occur on http://hg.netbeans.org/main in my case.
thanks for the info... marking issue as verified...