Bug 267045 - After restart of Eclipse whole workspace has compile errors
Summary: After restart of Eclipse whole workspace has compile errors
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 4.14 M3   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 11:33 EST by Sascha Theves CLA
Modified: 2019-11-21 09:19 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Theves CLA 2009-03-04 11:33:35 EST 
Build ID: I20080617-2000

Steps To Reproduce:
It`s hard to reproduce but sometimes if you restart Eclipse the workspace has compile errors. JDT Marker says: "java.lang.Object can not be resolved to a type"

sometimes the same for other Java built-in Objects, e.g. Enum.

The workaround for me was closing the project and reopen it and then call clean project.

This bug is a kind of blocker for me because I have to do the workaround for each project with such compile errors and that are about 50 in my workspace.


More information:
Comment 1 Frederic Fusier CLA 2009-03-04 11:56:27 EST 
Sounds like a duplicate of bug 255931...
Please give it a try with 3.4.2 and reopen in case of this assumption was wrong, thx

*** This bug has been marked as a duplicate of bug 255931 ***
Comment 2 Sascha Theves CLA 2009-03-09 08:43:42 EDT 
I tried now the eclipse M20090211-1700 build. But I run into the same problems. Here is the marker message:

"The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files."
Comment 3 Jerome Lanneluc CLA 2009-05-05 11:09:54 EDT 
Can you reproduce with a 3.5 build (ie. 3.5M7)?
Comment 4 Eclipse Genie CLA 2019-11-13 01:34:24 EST 
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 5 Stephan Herrmann CLA 2019-11-21 09:19:40 EST 
We'd need something reproducible to start working on this.