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 build contrib/hexeit. Then created a module suite in c:\tutorial\dev\HexeditSuite. In the wizard to create a wrapper module, I tried to create a wrapper module in c:\tutorial\dev\HexeditWrapper. When I pressed finish in the wizard, the attached exception was thrown; the dialog was not closed, but the directory was definitely created. I will attach the generated project - not sure what went wrong.
Created attachment 23381 [details] stack trace
Created attachment 23382 [details] what was generated
FYI C:\tutorial\nbsrc\contrib\hexedit>java -version java version "1.6.0-ea" Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b42) Java HotSpot(TM) Client VM (build 1.6.0-ea-b42, mixed mode, sharing)
steps to reproduce? does it always happen? it never does for me.
Assertion coming from masterfs; reassigning for eval.
Steps to reproduce: Do as I described above using contrib/hexedit. Later I did successfully do it; not sure what the problem is.
Raising priority - creating library wrapper modules is broken because of this. Do the following: - Start with a clean userdir - Get the libraries from the feedreader tutorial - rome-0.4.jar and rome-fetcher-0.4.jar - Put them in one directory somewhere on disk (not under CVS) - Create a new library wrapper module project - Call it "rome" - Select both jars as libs - Press Finish Assertion error is thrown.
You need to delete fetcher.properties from the root of rome-fetcher-0.4.jar (already filed separately). Downloads are from rome.dev.java.net. Just tried to reproduce on Linux, JDK 5, fresh user dir, dev sources from yesterday (but current apisupport/project). Followed Tim's instructions. Of course you have to make a suite, too. Worked fine for me. Mac OS X specific perhaps? Or Windows? My suspicion: NbModuleProjectGenerator.createSuiteLibraryModule indirectly calls FileUtil.createData with a path containing File.separator, whereas it should always be using '/'. Perhaps on Windows this confuses masterfs into creating the file but then not knowing where it was. If this is the problem, (1) NbMPG.cSLM should be fixed, (2) masterfs should be corrected to throw an IOException if someone attempts to use '\\' as a path separator for file objects contrary to the API.
I am seeing the same thing, using netbeans-4_2-qbuild-bin-200508091556-9_Aug_2005_1556.zip and netbeans-4_2-daily-bin-200508171800-17_Aug_2005_1800.zip with JDK 5.0_04 und Windows 2000. Attaching stacktrace.
Created attachment 24076 [details] Additional stacktrace.
Raising to P1, because cannot write a module for 4.2 because of this bug.
Exactly as Jesse expected.
Will we get a fix on Monday?
Since I've hit this problem on Windows, probably the \ is the problem.
Fixed: /cvs/apisupport/project/src/org/netbeans/modules/apisupport/project/NbModuleProjectGenerator.java,v new revision: 1.36; previous revision: 1.35 /cvs/openide/masterfs/src/org/netbeans/modules/masterfs/MasterFileObject.java,v new revision: 1.45; previous revision: 1.44 /cvs/openide/masterfs/src/org/netbeans/modules/masterfs/filebasedfs/fileobjects/FolderObj.java,v new revision: 1.12; previous revision: 1.11
Reopening, because this is not fixed in netbeans-4_2-daily-bin-200508221800-22_Aug_2005_1800.zip. Attaching messages.log from wrapping junit.jar.
Created attachment 24140 [details] messages.log from wrapping junit.jar
You probably got a build without the fix. The stack trace from NbModuleProjectGenerator does not match current sources. Try the next one or build from sources and check again.