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.
[ BUILD # : 200807251401 ] [ JDK VERSION : 1.6.0_07 ] In 6.5 M1 this test processed without problems. Here you find the source: https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio- charset-enhanced/branches/milestone1/test/SpeedTest.java?rev=&view=mar kup You can download the project from here: - https://java-nio-charset-enhanced.dev.java.net/ - https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio- charset-enhanced/trunk/ current head is here: - https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio- charset-enhanced/branches/milestone1/ I have installed 200807251401 and copied the settings from .netbeans\6.5m1 before 1st start. Note: there have happend changes in nbproject folder after start of 200807251401, so I attach it too.
Created attachment 65823 [details] JUnit test fails
Created attachment 65824 [details] modified nbproject folder
maybe related to compile on save? can you check the project's properties dialog, panel Build/Compiling? reassigning for evaluation to jlahoda jlahoda: please note the project has -Xbootclasspath/p:build/classes added to compiler options.
I have switched off 'compile on save'. Result: now it works. :-) Thanks for your hint. Concerning -Xbootclasspath/p:build/classes : tzezula advises me to fork VM for javac target by override the -init-macrodef-javac target and add fork="true" attribute to it. I didn't have any success with this. See my last comment here: http://www.netbeans.org/issues/show_bug.cgi?id=130352 Can you give me some additional suggestions for this?
The test failures I was able to reproduce were because of incorrect working directory - which has been already fixed as issue #141639. Not sure if there are any other problems that can be fixed in the compile-on-save approach - if you need to do something extraordinary, you may need to disable the CoS and use the traditional build scripts. *** This issue has been marked as a duplicate of 141639 ***