Bug 56316 - JavaProject exists should not populate
Summary: JavaProject exists should not populate
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-26 04:49 EST by Philipe Mulet CLA
Modified: 2004-05-18 11:27 EDT (History)
0 users

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 Philipe Mulet CLA 2004-03-26 04:49:01 EST 
Build 20040326

When asking a project if it exists, it creates its info, and thus triggers all 
classpath initialization. It should just check whether resource exists and has 
java nature.

Along this line, we should double check our implementations for elements which 
have an associated resource. They should only check that the resource exists 
and is on classpath... unless this is breaking some contracts.
Comment 1 Jerome Lanneluc CLA 2004-03-30 06:10:09 EST 
Changed JavaProject.exists() to just check if the project has the Java nature 
(and is accessible). 
Also added Openable.exists() that checks that the parent and the resource exist 
(if it has a resource) without opening the element.
Comment 2 Frederic Fusier CLA 2004-05-18 11:27:49 EDT 
Verified for 3.0 M9 with build I200405180816.