Bug 3968 - Rename refactoring for overridden methods should be more supportive (1GFAYM4)
Summary: Rename refactoring for overridden methods should be more supportive (1GFAYM4)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 23:03 EDT by Erich Gamma CLA
Modified: 2002-02-08 11:18 EST (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 Erich Gamma CLA 2001-10-10 23:03:51 EDT 
EG (6/14/01 10:46:47 AM)
	1) try to renaming a method that is overridden from a base class
	2) the precondition check tells me that I should do this in the most abstract class.
	I'm not told what this abstract class is. If we can't compute it easily we should
	offer to open the type hierarchy on this type.

NOTES:

AK (8/15/2001 4:14:27 PM)
	waiting for: 1GII6W0: ITPJCORE:WINNT - search for method declarations in hierarchy does not work as expected
Comment 1 Adam Kiezun CLA 2002-02-08 11:18:39 EST 
fixed 20020208