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

Bug 258116

Summary:

Object was not resolved inside my projects

Product:

[Eclipse Project] JDT

Reporter:

David Audel <david_audel>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

remy.suen

Version:

3.5

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
David's variablesAndContainer.dat	none

Description David Audel

2008-12-09 11:24:20 EST

build I20081208-1800

I started eclipse with a workspace which contains jdtcore test projects as source.
All the projects have lot of errors because Object cannot be resolved.

The exact error message is:
"The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files"

The problems disappeared after closing and reopening the projects and then did a Clean on the projects.


I cannot reproduce this problem another time.

Comment 1 Remy Suen

2008-12-09 11:39:34 EST

I see this all the time and I usually fix it by cleaning, closing/reopening the project, and/or restarting Eclipse. It's an intermittent problem I hear once in a while on IRC also. I don't think I've heard anyone with reproducible steps although I recall a similar bug filed at PDE (I think?).

Comment 2 Jerome Lanneluc

2008-12-09 12:13:47 EST

Remy, are you using 3.4.1? If you do, could you please try the patch from bug 255931 comment 12, and report in bug 255931 if it helps.

Comment 3 Jerome Lanneluc

2008-12-09 12:15:45 EST

Created attachment 119930 [details]
David's variablesAndContainer.dat

Looking at this metadata, it appears that some projects were saved with no classpath entries for the JRE Container.

Comment 4 Remy Suen

2008-12-09 12:18:18 EST

(In reply to comment #2)
> Remy, are you using 3.4.1? If you do, could you please try the patch from bug
> 255931 comment 12, and report in bug 255931 if it helps.

Sorry Jerome, "all the time" was an exaggeration and I don't know why I typed that. I got hit by it last week but that was on a recent I build (like I1202 or something).

Comment 5 Eclipse Genie

2020-03-18 18:23:02 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.