Bug 91804 - JavaProject.isOnClasspath(IJavaElement) should avoid resolving classpath
Summary: JavaProject.isOnClasspath(IJavaElement) should avoid resolving classpath
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-04-18 17:58 EDT by Jerome Lanneluc CLA
Modified: 2005-05-12 07:21 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 Jerome Lanneluc CLA 2005-04-18 17:58:06 EDT 
I20050413

JavaProjec.isOnClasspath(IJavaElement) should use the raw classpath when
possible (e.g. if the element is a compilation unit)
Comment 1 Jerome Lanneluc CLA 2005-04-19 17:49:35 EDT 
As of I20050419, isOnClasspath is no longer called by JDT UI on startup. This
lowers the priority of this bug.
Comment 2 Jerome Lanneluc CLA 2005-04-22 04:06:15 EDT 
Changed JavaProject#isOnClasspath(IJavaElement) to first get the raw classpath
and see if the element is on the raw classpath. If it is a compilation unit,
returns false. Otherwise look at the resolved entries.
Comment 3 Frederic Fusier CLA 2005-05-12 07:21:56 EDT 
Verified for 3.1 M7 using build I20050509-2010 + jdt.core HEAD.