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.
After checking out stable_nowww, I cannot build the IDE anymore: BUILD FAILED .../nball/nbbuild/build.xml :148: java.io.IOException: Duplicated module org.netbeans.lib.terminalemulator: found in http://hrebejk-ws.czech:8080/hudson/job/TasklistSlave/ws/nball/core/term and http://hrebejk-ws.czech:8080/hudson/job/TasklistSlave/ws/nball/cnd/term
Is anybody working on this ? I see Target Milestone=future ;(
This was already resolved yesterday... BTW this is not P1... There is simple workaround, to checkout it using module list. *** This issue has been marked as a duplicate of 100606 ***
Michal, are you really, really, really sure this is duplicate of issue #100606 and is fixed (ie. if I do "cvs checkout stable; cd nbbuild; ant" it will build the IDE)? BTW: if I use one of the recommended ways (http://www.netbeans.org/community/sources/cvs.html, section "Using CVS on Windows") to checkout the source and cannot build the IDE as the result, it is a P1, IMO.
Michal, I deleted whole cnd module from my local sources and did checkout once again - it fails with the same log, this morning.
OK, I'm reopening it. There are two modules with the same name one is core/term second is cnd/term. One of those two need to change its name. So this has nothing to do with the building. Build just found that there is an issue. I'm also changing the desc.
OK, so what is currently supported way to build the _whole_ IDE? Because of all those problems with socks last couple of days my CVS repository got seriously broken, so I did complete checkout to be safe and now this. I'm not able to do my work for last two days! Is there anybody responsible for this module? This is P1 affecting building of the IDE.
One possible workaround is to delete "cnd" module (not needed for the (Java) NetBeans IDE) after checkout.
I've fixed the stable, stable_nowww, standard, standard_nowww and localizable_nowww alises by removing cnd from them. This is temporary workaround to avoid duplicated CNB lying under the same root of working directory. The issue with duplicated CNB in *source code* is not resolved, in other words this issue deserves to be kept open. Setting target milestone 6.0M10. Setting this issue as NB6-M10 blocker by setting block for NB6-M10 blocker issue 100816 . Removing Build Engineering from Cc:, our part has been done in issue 100770 .
Can the priority of this item be lowered to P3, with the understanding that a permanent fix is planned for May timeframe?
I understand there is some backlash against the cnd group over this issue. I'd like to go on record as saying that the root cause of this problem was that cnd was added to the netbeans builds without our being informed. This happened on Tuesday. As a non-netbeans-build module our commit rules were very different than the netbeans commit rules. Had we been informed we were now part of netbeans builds, the commit adding term to cnd would not have been merged to the trunk and would not have broken the netbeans build. I'm really surprised such a major change was made without the cnd team being informed! FYI, a proposed solution was sent to Jan Lahoda (the issue filer) within 90 minutes of my receiving the issue. My appologies for not updating the IZ, but I thought direct email would be faster. If nobody objects, I'd like to downgrade to P3 until we (the cnd team) finish cnd 5.5.1 and start actively working on cnd 6.0. At that point I'll have the time to work on a permanent solution.
Downgrading to P3 per email from Jan Lahoda and Rudolf Balada telling me the stable_nowww build issues are temporarily resolved. I will work on a permanent solution for 6.0M10 (after CND 5.5.1 FCS').
This was resolved by removing core/term from the repository. So, IMO this is not a stopper for M10 and should be closed fixed or removed as a blocker from the M10 umbrella issue 106361.
It is OK with me to close this issue.
Closing as fixed since core/term has been removed from cvs and fresh checkouts and builds are working.
Could you please verify this issue for the latest M10 build? Thanks.
> Could you please verify this issue for the latest M10 build? Thanks. This is a build issue. There wouldn't be any working m10 builds if it were not resolved. But I double checked that core/term is now empty and that release60-m10 builds and uses cnd/term.