Summary: | JavaProject.isOnClasspath(IJavaElement) should avoid resolving classpath | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | performance |
Version: | 3.1 | ||
Target Milestone: | 3.1 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Jerome Lanneluc
2005-04-18 17:58:06 EDT
As of I20050419, isOnClasspath is no longer called by JDT UI on startup. This lowers the priority of this bug. 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. Verified for 3.1 M7 using build I20050509-2010 + jdt.core HEAD. |