Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 287770

Summary: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
Product: [Eclipse Project] JDT Reporter: Andi Rustandi Djunaedi <andird>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: kentarou, Olivier_Thomann
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Andi Rustandi Djunaedi CLA 2009-08-26 22:57:04 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:03 SGT 2009
Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
Severity: Error
Product: Eclipse 1.2.0.20090618-0904 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.core.resources
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.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2552)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1773)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2652)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2561)
at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2662)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1861)
at org.eclipse.jdt.internal.core.ExternalFoldersManager.refreshReferences(ExternalFoldersManager.java:268)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1890)
at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:269)
at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:307)
at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1519)
at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor$2.runInWorkspace(IDEWorkbenchAdvisor.java:372)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Olivier Thomann CLA 2009-09-10 13:04:22 EDT

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