Community
Participate
Working Groups
Build ID: cvs version v_853 Whenever the batch compiler catches an exception the ProcessTaskManager throws NPE while trying to report the exception. You probably shouldn't shutdown() the ProcessTaskManager *before* delegating to this.compiler.handleInternalException() because shutdown nulls the field this.compiler ;-/
I also got it on Windows Vista: !ENTRY org.eclipse.team.cvs.core 4 4 2008-04-21 10:05:24.897 !MESSAGE The state of /org.eclipse.jdt.core.tests.model/workspace/Formatter/test714/A_out.java has been changed concurrently. Exception in thread "Compiler Processing Task" java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:131) at java.lang.Thread.run(Thread.java:619)
Fixed the NPE - no need to null out the compiler slot Released for 3.4M7 Still need to find out the original cause of the message: /org.eclipse.jdt.core.tests.model/workspace/Formatter/test714/A_out.java has been changed concurrently
Verified for 3.4M7 using I20080427-2000.