Bug 56316

Summary:	JavaProject exists should not populate
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	3.0 M9
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Philipe Mulet

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

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

2004-05-18 11:27:49 EDT

Verified for 3.0 M9 with build I200405180816.