Bug 10057 - References To Hierarchy
Summary: References To Hierarchy
Status: CLOSED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-21 09:22 EST by Dani Megert CLA
Modified: 2004-06-30 05:42 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 Dani Megert CLA 2002-02-21 09:22:57 EST 
If a method T.m() is selected then "Reference" search reports only exact matches
to T.m(). This often results in 0 results (e.g. if T implements an interface I
or extends another type).

A new search (References to Hierarchy) should return all references to m() in
the hierarchy (including interfaces and subtypes) of T.
Comment 1 Dani Megert CLA 2003-09-19 03:42:53 EDT 
Testing a link: see bug 10057, comment 0.
Comment 2 Dani Megert CLA 2004-01-22 05:18:06 EST 
reassigning
Comment 3 Thomas M??der CLA 2004-06-29 11:36:48 EDT 
I figure this is more complicated than it sounds. Still a good idea, though.
Comment 4 Dirk Baeumer CLA 2004-06-30 05:33:45 EDT 
Daniel,

I did some testing and for me this works as expected:

public abstract class A {
	public abstract void foo();
}
public interface I {
	public void foo();
}
public class B extends A implements I {
	public void foo() {
	}
}
public class Ref {
	public void bar() {
		I i= null;
		A a= null;
		B b= null;
		
		i.foo();
		a.foo();
		b.foo();
	}
}

- searching for references to B#foo gives three matches
- searching for references to I#foo gives two matches
- searching for references to A#foo gives two matches

So the only problem I see is the marriage of convenience case.
Comment 5 Dani Megert CLA 2004-06-30 05:42:36 EDT 
looks like this has been improved.