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

Bug 106731

Summary: The type java.lang.Object cannot be resolved. It is indirectly
Product: Community Reporter: Renato Steiner <honato11>
Component: BugzillaAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Renato Steiner CLA 2005-08-11 06:15:18 EDT
Problem:
--------
The type java.lang.Object cannot be resolved. It is indirectly referenced from
required .class files

Problem cause:
--------------
JDK1.3.1 was configured at Preferences.Java.Installed JREs, but the .classpath
file contained: 

 <classpathentry exported="true" kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JDK
1.3.1"/>

This entry was never updated even though a new JDK was added. After
changing the name to JDK 1.3.1 it worked and best is, the error
message never appeared again even after changing back the name to
JDK1.3.1 (the .classpath file was updated correctly). Seems to be an
Eclipse 3.1 bug.

Background-Infos: 
-----------------
This may happen when a project is imported into
Eclipse from scratch for which  a .classpath file aready exists.

Problem solution: 
-----------------
Check .classpath file and name your JRE exactly as
you see in StandardVMType/...

The cool thing is that after changing the name to JDK 1.3.1 and then back to 
JDK1.3.1 it worked. 

Task for the eclipse developers
-------------------------------
Take care that .classpath file is updated correctly if an eclipse project is
imported and a JRE is added.
Comment 1 Eclipse Webmaster CLA 2005-08-11 08:37:38 EDT
The Community component of Bugzilla if for reporting problems with the
eclipse.org infrastructure.

I suggest you post your problem to one of our newsgroups - for instance, the
eclipse.newcomer or eclipse.platform (http://eclipse.org/newsgroups/) to make
sure you have really found a bug before submitting a bug report.

They will also guide you to the right Bugzilla product to report your bug.

D.