Bug 81783

Summary: Call hierarchy reports wrong references to private method
Product: [Eclipse Project] JDT Reporter: Martin Winter <martin.winter>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.0.1   
Target Milestone: 3.1 M3   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Martin Winter CLA 2004-12-22 09:08:16 EST 
When opening the call hierarchy for a private method, references are shown to 
same-named methods in subclasses.

Example: Consider a user class extending java.lang.Thread. The extended class 
contains a method 

   protected void exit();

When opening the call hierarchy for the private void exit() of 
java.lang.Thread, the references to the protected method of the extended class 
are shown.

Example class to reproduce the bug:

class Test
{
    protected void exit(){}
    public void foo() { exit(); }
}

Now open java.lang.Thread and from there, open the call hierarchy for 
java.lang.Thread.exit(). The call hierarchy states, that Thread.exit would be 
called from Test.foo.
Comment 1 Frederic Fusier CLA 2004-12-22 09:53:49 EST 
This bug has been fixed in 3.1 stream since 3.1 M3...
However, as this is neither a critical nor a major bug, I don't think this fix
will be backported to 3.0.2 stream (except if there's a real need...)


*** This bug has been marked as a duplicate of 70827 ***