Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: dev
-
Fix Version/s: 0.9.8
-
Component/s: None
-
Labels:None
-
Environment:Eclipse 3.4.1
-
Number of attachments :
Description
Happens on Eclipse restart with the latest dev build
– Error Details –
Date: Mon Jan 05 10:35:00 EST 2009
Message: An internal error occurred during: "Initializing Java Tooling".
Exception Stack Trace:
java.lang.NullPointerException
at org.maven.ide.eclipse.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:42)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2371)
at org.eclipse.jdt.internal.core.JavaModelManager$13.run(JavaModelManager.java:2301)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2317)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1679)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3398)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Is this the only exception? I get this exception too, but for me it always comes with "timed out waiting (5000ms) for thread" OSGi classloader exception. For me the workaround is to close all java editors and restart eclipse.