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.
For a while I am trying to identify reasons for recent failures in the netbinox tests. Looks like the JUnit tests of a module in a suite get empty -Xbootclasspath/p: argument. As far as I can tell this is interpreted as "add current directory on boot classpath", at least on 1.6.0_20 and also on recent OpenJDK. I think this is result of 8a4998f46c4c. The previous state probably ignored the non-existing directory, but the current adds current dir. Please modify common.xml to skip any -Xbootclasspath/p: arguments if they are not necessary.
Created attachment 100261 [details] Proposed patch
I actually initially considered doing that, but considered -Xbootclasspath/p: to be harmless, and this approach will break if the JDK path has a space in it. Oh well, Ant is too weak to do better. core-main #bba9f36fe852
Integrated into 'main-golden', will be available in build *201006220001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/bba9f36fe852 User: jtulach@netbeans.org Log: #187866: do not pass "-Xbootclasspath/p:" to tests.
Re. "space in path" - maybe we could use <jvmargs value="${args}"/> and just find some silly fallback like args="-Dnothing.on.bootclasspath=true"
Might be an improvement. No strong opinion. Probably Windows users who would be likely to suffer from space-in-path issues.