Bug 106806 - The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
Summary: The type java.lang.Object cannot be resolved. It is indirectly referenced fro...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Update-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-11 23:34 EDT by Renato Steiner CLA
Modified: 2020-12-22 22:12 EST (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 Renato Steiner CLA 2005-08-11 23:34:01 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/...

Task for the eclipse developers
-------------------------------
Take care that .classpath file is updated correctly if an eclipse project is
imported
and a JRE is added. 


Eclipse bugzilla case eroeffnet unter honato11@gmail.com. 
Bug 106731 has been added to the database

Eclipse Build
-------------

Version: 3.1.0
Build id: I20050627-1435

Kind Regards, 

Renato Steiner
Comment 1 Branko Tripkovic CLA 2006-06-22 19:30:23 EDT
I am not sure where install/update comes into play here?
Comment 2 Renato Steiner CLA 2006-06-22 21:03:58 EDT
(In reply to comment #1)
> I am not sure where install/update comes into play here?
> 
What do you mean with install/update? 
Comment 3 Branko Tripkovic CLA 2006-06-23 12:55:08 EDT
Well, you opened this bug against Eclipse's Install/Update component, but I can't see anywhere that you are using it.
Comment 4 Renato Steiner CLA 2006-06-23 14:13:12 EDT
Got your point. I might have choosen the wrong component. Anyway the bug is very old and maybe not even existing andymore in the current code base. I suggest to close the bug - works for me. 

Kind Regards
Renato 
Comment 5 Branko Tripkovic CLA 2006-06-23 14:14:26 EDT
Thanks Renato.
Comment 6 Daeyong Kwon CLA 2020-12-22 22:12:31 EST
When I start up Eclipse, this error is visible in the first line of code which states the package:

The type java.lang.String cannot be resolved. It is indirectly referenced from required .class files

I do not believe I have done anything wrong, other than going into my libraries and accidentally deleting some things. I had to update to MacOS Big Sur, and did not have the storage. After deleting many items from my Mac, I ran Eclipse again, and this error immediately popped up again. I've tried the suggested uninstalling the JRE System Library and reinstalling it, but to no avail. Can somebody please help me?