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.
Summary: | java.io.IOException: org.netbeans.DuplicateException: C:\Program Files\NetBeans Dev 200808141419\maven1\modules\org-netbeans-modules-maven-gsf.jar is a duplicate of C:\Program Files\NetBeans Dev 20080 | ||
---|---|---|---|
Product: | platform | Reporter: | vkelman <vkelman> |
Component: | Module System | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=25556 | ||
Issue Type: | DEFECT | Exception Reporter: | 25556 |
Attachments: | stacktrace |
Description
vkelman
2008-08-15 03:19:06 UTC
Created attachment 67487 [details]
stacktrace
not sure how this is maven related. it looks like an issue in module system. From the logs, it looks like the DuplicateException is just a side-effect of the root problem, an ISE checking whether an eager module can be enabled - which in turn seems likely to be caused by newly installed modules being created in arbitrary order. Not sure if fix addresses the problem since there are no apparent steps to reproduce it. core-main #3c97ce25b847 Integrated into 'main-golden', available in build *200808191401* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/3c97ce25b847 User: Jesse Glick <jglick@netbeans.org> Log: Enabling available eager modules whenever any new module is created. Looks like it will fix #144005, though it is not clear how that can be reproduced. Found a simple way to reproduce (and confirm that fix works): 1. ant -Dcluster.config=basic clean build-nozip tryme 2. Tools > Plugin Manager 3. Under Available, select Java Profiler and Install. Trying a different fix - just deleting code to enable eager modules as they are created. It seems this is not really necessary anyway, since most client code which would create new modules will also try to enable some of them, which will have the effect of enabling any available eager modules in batch mode, with much less overhead. core-main #8c44699b4277 *** Issue 143729 has been marked as a duplicate of this issue. *** Integrated into 'main-golden', available in build *200808201401* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/8c44699b4277 User: Jesse Glick <jglick@netbeans.org> Log: #144005 cont'd: do not try to enable eager modules when they are created. |