Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 287769 - An internal error occurred during: "Initializing Java Tooling".
Summary: An internal error occurred during: "Initializing Java Tooling".
Status: CLOSED DUPLICATE of bug 276111
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-26 22:56 EDT by Andi Rustandi Djunaedi CLA
Modified: 2009-09-10 13:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andi Rustandi Djunaedi CLA 2009-08-26 22:56:40 EDT
What steps will reproduce the problem?
1. Start the eclipse, and select the workspace
2. When starting up this error message will appear
3. This have happens many times before, altough I don't see any side effects yet when I continue using eclipse.


-- Error Details --
Date: Thu Aug 27 10:46:05 SGT 2009
Message: An internal error occurred during: "Initializing Java Tooling".
Severity: Error
Product: Eclipse 1.2.0.20090618-0904 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=I20090611-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product


Exception Stack Trace:
java.lang.NullPointerException
at org.eclipse.jdt.internal.junit.buildpath.P2Utils.getBundlesFromFile(P2Utils.java:125)
at org.eclipse.jdt.internal.junit.buildpath.P2Utils.readBundles(P2Utils.java:69)
at org.eclipse.jdt.internal.junit.buildpath.P2Utils.findBundle(P2Utils.java:166)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport$JUnitPluginDescription.getLibraryEntry(BuildPathSupport.java:70)
at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport.getJUnit3LibraryEntry(BuildPathSupport.java:162)
at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.getNewContainer(JUnitContainerInitializer.java:101)
at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.initialize(JUnitContainerInitializer.java:90)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2608)
at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2514)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2554)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1773)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3410)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Robert Olofsson CLA 2009-09-04 03:00:25 EDT
I can reproduce this error on two machines I have, both running Windows XP.

Session Data:

eclipse.buildId=I20090611-1540
java.version=1.6.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=sv_SE
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
Comment 2 Olivier Thomann CLA 2009-09-10 13:04:38 EDT

*** This bug has been marked as a duplicate of bug 276111 ***