Bugzilla – Full Text Bug Listing
| Summary: | NameLookup#findSecondaryType(...) should consider the classpath order | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
Not critical, defer post 3.2 Reopen as LATER is deprecated... Set as P5 bugs which have be unchanged for more than 2 years... This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
I20060110 If you have the following project: P +- src1 X.java public class X {} class Y {} +- src2 X.java public class X {} class Y {} NameLookup#findSecondaryType(...) may find src2/X.java/Y instead of src1/X.java/Y since the last indexed secondary type wins in the cache.