Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 290360 - [JUnit] NullPointerException on start, org.eclipse.jdt.internal.junit.buildpath.P2Utils.getBundlesFromFile
Summary: [JUnit] NullPointerException on start, org.eclipse.jdt.internal.junit.buildpa...
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-09-24 03:20 EDT by Mauro Molinari CLA
Modified: 2009-09-24 04:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mauro Molinari CLA 2009-09-24 03:20:06 EDT
Almost every other time, for some time on, I have being experiencing a NullPointerException while starting Eclipse.

I'm using Eclipse 3.5.0, Build id: I20090611-1540, 64-bit version under Windoes XP x64 Edition.

The error is always at org.eclipse.jdt.internal.junit.buildpath.P2Utils.getBundlesFromFile(P2Utils.java:125), however stack traces can be a bit different. An example of a NPE stack trace follows.

Unfortunately, this problem is not always reproducible. To reproduce, I have just to start Eclipse. It seems to happen the first time I start it when I arrive at work in the morning.

-- Error Details --
Date: Thu Sep 24 09:02:53 CEST 2009
Message: An internal error occurred during: "Initializing Java Tooling".
Severity: Error
Product: Eclipse Platform 3.3.200.v200906111540 (org.eclipse.platform.ide)
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=I20090611-1540
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT
Command-line arguments:  -os win32 -ws win32 -arch x86_64


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.getJUnit4LibraryEntry(BuildPathSupport.java:169)
at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.getNewContainer(JUnitContainerInitializer.java:103)
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 Frederic Fusier CLA 2009-09-24 04:06:04 EDT
Move to JDT/UI
Comment 2 Dani Megert CLA 2009-09-24 04:12:16 EDT

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