Community
Participate
Working Groups
Build 20030825 1. Create package p1 2. Create cu A.java in p1: package p1; public class A { } 3. Create package p2 4. Create cu B.java in p2: package p2; public class B { Object p1; } 5. Create cu C.java in p2: package p2; import p1.A; public class C extends A { } 6. Select field B.p1 and search for references in hierarchy Observe: p2/C.java is found as a potential match in SearchEngine.search (IWorkspace, ISearchPattern, IJavaSearchScope, IJavaSearchResultCollector) The only reference to 'p1' is in 'import p1.A;'. We might want to optimize out this case.
Is this working for free given your latest changes ?
Jerome: I cannot reproduce this using the latest HEAD contents, can you?
Yes, I can still reproduce using the latest HEAD content.
Just to clarify... it is NOT a potential match showing up in the UI. The question is why is an import statement adding a generic reference to 'p1' to the index (which then needs to be resolved to see if its a field ref), when it clearly can only be either a package or type ref.
I don't see any obvious reason for it, though with 1.5 we will have to deal with static imports which are likely going to introduce this kind of ambiguity.
Deferring post 3.1
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
