Bug 252338 - JRE disappears from build path on MacOS Leopard unpredictably
Summary: JRE disappears from build path on MacOS Leopard unpredictably
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2008-10-28 08:08 EDT by benson margulies CLA
Modified: 2013-12-06 09:00 EST (History)
2 users (show)

See Also:

Attachments
a classpath and a project. (10.00 KB, application/octet-stream)
2008-11-17 10:03 EST, benson margulies CLA 		no flags Details
View All 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 benson margulies CLA 2008-10-28 08:08:45 EDT 
Build ID: M20080911-1700

Steps To Reproduce:
I have a workspace with a large collection of projects. It's set up for me by the maven eclipse plugin.

From time to time, I will start eclipse, and find that \some/ of the projects have errors: "Unable to find java.lang.Object".

I can fix this by opening up the projects build path, and switching from "JRE System Library [JVM 1.5 MacOS System Default]" to the corresponding execution environment.

I can then change the build path back, and the error does not return.



More information:
Obviously, this isn't a great repro. If you can give me some instructions for what to debug to try to find out what is happening, I'll do it.
Comment 1 Jerome Lanneluc CLA 2008-11-17 07:51:13 EST 
Moving to JDT/Debug for investigation
Comment 2 benson margulies CLA 2008-11-17 09:50:33 EST 
I don't know why you moved this to Debug. The problem exhibits in the project explorer tree -- the constant incremental build suddenly covers the tree with red 'x' annotations and the Problems fills up with missing java.lang.Object complaints.
Comment 3 Darin Wright CLA 2008-11-17 09:57:28 EST 
JDT Debug is responsible for binding system libraries to projects. It could be a bug in the 'JRE classpath container' that performs this binding.

What sort of projects are these? Pure Java, plugins, etc?
Comment 4 benson margulies CLA 2008-11-17 09:59:53 EST 
Pure java.

I'll attach a classpath and a project.
Comment 5 benson margulies CLA 2008-11-17 10:03:06 EST 
Created attachment 118050 [details]
a classpath and a project.
Comment 6 benson margulies CLA 2009-02-03 09:51:09 EST 
I just had this happen to me on the current 3.5 Milestone build. Is there anything I can do to extract information on this to chase the problem down?
Comment 7 benson margulies CLA 2009-02-03 09:56:29 EST 
By the way, the new failure is on PDE projects.
Comment 8 Darin Wright CLA 2009-06-17 09:53:11 EDT 
Next time this happens, please try to expand the "JRE System Library" element in the package explorer (and take a screen shot).
Comment 9 Michael Rennie CLA 2013-12-06 09:00:07 EST 
We have made a lot of changes since 3.4.1 around JRE/JDK support on Mac OS, if you can reproduce in 4.4 please reopen with steps, etc.

Closing worksforme without more to go on