Bug 182204 - Deleting a JRE referenced by container does not result in unbound container problem
Summary: Deleting a JRE referenced by container does not result in unbound container p...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M7   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-12 15:10 EDT by Darin Wright CLA
Modified: 2007-04-27 06:19 EDT (History)
0 users

See Also:


Attachments
Proposed fix and regression test (6.60 KB, patch)
2007-04-16 12:26 EDT, Jerome Lanneluc CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2007-04-12 15:10:06 EDT
I20070410-1043

Scenario 1:
* Launch a workspace
* Create a Java project bound to a specific JRE (say JDK1.4.2)
* Create a class in the project
* Delete the JRE from the Installed JRE's page

> Two errors show up:

Severity and Description	Path	Resource	Location	Creation Time	Id
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project		Warn	Unknown	1176404482796	8751
The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files	Warn/src	Main.java	line 1	1176404482796	8752

The quick fix for "Object cannot be resolved" does not include the "select system library" fix from JDT debug, as the problem marker is not of the type "CP_CONTAINER_PATH_UNBOUND".

Should this result in an ubound container error?


Scenario 2:
* Launch a workspace
* Create a Java project bound to a specific JRE (say JDK1.4.2)
* Create a class in the project
* Close the workspace
* Rename the JRE in the file system
* Re-start the workspace

> No errors appear for the project, but the classpath is unbound. Triggering a build results in 1 error (cannot find java.lang.Object), but again it is not an unbound classpath. Should it be?

I can't seem to create a CP_CONTAINER_PATH_UNBOUND error to test our contributed quick fix.
Comment 1 Jerome Lanneluc CLA 2007-04-16 12:26:06 EDT
Created attachment 63917 [details]
Proposed fix and regression test
Comment 2 Jerome Lanneluc CLA 2007-04-18 09:07:45 EDT
Fix and test released for 3.3M7 in HEAD.
Comment 3 Eric Jodet CLA 2007-04-27 05:22:24 EDT
(In reply to comment #2)
Verified for 3.3 M7 using build I20070427-0010