Product Version = NetBeans IDE 7.2 (Build 201207171143)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_26
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.1-b02
1. Create new clean netbeans module project (File > New Project... > Netbeans Modules > Module) targeting Development IDE platform
2. Add Java Hint file (File > New File... > Module Development > Java Hint) with Fix
3. Add missing Unit Test Libraries (JUnit 4 was installed together with IDE)
4. Add Hava Hints Test API as unit test library
5. Test the project
Created attachment 125523 [details]
When switching to JDK_1.7 as Java Platform the error doesn't reproduce and the tests runs OK.
Created attachment 125524 [details]
Project Test Build Output
I apologize for inconvenience, but this:
must be added to the nbproject/project.properties of the project (as described in the comment in the generated test). That will ensure the bootclasspath is tweaked correctly, but the apisupport wizard infrastructure does not allow to do that from the wizard.
In my case even with
the issue could be reproduced on my system. This line was in the project.properties when I was posting a bug.
This applies even to 7.3 beta I have on my PC.
Product Version: NetBeans IDE 7.3 Beta (Build 201210011125)
Java: 1.6.0_26; Java HotSpot(TM) 64-Bit Server VM 20.1-b02
System: Windows 7 version 6.1 running on amd64; Cp1252; en_GB (nb)
Sorry, I did not understand from the description that you used the switch. I will check once I get to a Win 7 box - but in the mean time, if you could try to run the build with "-d" passed to ant and attach the output, that could shed some light on the problem.
Created attachment 125714 [details]
command line output on initial system configuration
Created attachment 125715 [details]
ant output on initial configuration
Created attachment 125716 [details]
command line output with JAVA_HOME set to JDK6
Created attachment 125717 [details]
ant output with JAVA_HOME set to JDK6
Here are the builds with "-d" option:
1. build_command_line.log - is the command I have typed in command window without any modifications to my system
build.log - is the output of ant utility
Note: there was a warning about JAVA_HOME not set in command line. So next I have set the variable to JDK6 and JDK7
2. build_jdk6_command_line.log - is the command after JAVA_HOME was set to JDK6
build_jdk6.log - is the output in this case
3. When the JAVA_HOME is set to JDK7 everything runs OK
Luckily does not seem to be related to Windows (I was able to run tests there without problems), which would be harder for me to debug, but rather to path with spaces, and is reproducible on Linux as well.
Created attachment 126387 [details]
I have attached a proposed patch:
I can commit it, but needs to be reviewed by the NB harness and buildsystem developers before that.
I can't integrate the patch without an automated test included in a daily running test suite which would fail right now and will succeed after the patch is integrated.
Translation to normal English: I don't have any clue of what is going on.
(In reply to comment #15)
> I can't integrate the patch without an automated test included in a daily
> running test suite which would fail right now and will succeed after the patch
> is integrated.
If you expect such a test from me, then I would ask you to point me to existing test suite that I can extend.
Unless you can describe how to emulate the failure, I can't accept the patch.
Created attachment 126497 [details]
1. Make a copy of NetBeans in a directory with a space, e.g.:
4. Open in the IDE from step 1, and choose "Test" from the project's pop-up menu. An error like this will appear:
5. Place another copy of NetBeans into a directory without a space, repeat step "4." - no error will appear.
(BTW: you would basically get the same by following the original steps, with the addition of adding "requires.nb.javac=true" into nbproject/project.properties mentioned in #c4 and #c5.)
I've did all I should:
~/tmp/219651$ ./net\ beans/bin/netbeans --userdir u\ d/
and the test seem to notice the space:
Scanning for modules in /home/jarda/tmp/219651/net beans/webcommon
Scanning for modules in /home/jarda/tmp/219651/net beans/apisupport
Scanning for modules in /home/jarda/tmp/219651/net beans/websvccommon
Scanning for modules in /home/jarda/tmp/219651/net beans/nb
Scanning for modules in /home/jarda/tmp/219651/net beans/dlight
Scanning for modules in /home/jarda/tmp/219651/net beans/cnd
Scanning for modules in /home/jarda/tmp/219651/net beans/enterprise
Scanning for modules in /home/jarda/tmp/219651/net beans/java
Scanning for modules in /home/jarda/tmp/219651/net beans/ide
Scanning for modules in /home/jarda/tmp/219651/net beans/harness
Scanning for modules in /home/jarda/tmp/219651/net beans/profiler
Scanning for modules in /home/jarda/tmp/219651/net beans/platform
but at the end the tests succeed. Maybe it will be easier if I stop by on Monday and let you show the problem to me?
And did you try on JDK6? But sure, stop by, but better on Tuesday or Wednesday
Reproduced the failure on JDK6 - after applying the patch, the failure is gone.
Integrated into 'main-golden', will be available in build *201212200001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jan Lahoda <firstname.lastname@example.org>
Log: #219651: More robust handling of space in installaton path.