Bug 37574 - Rename published method refactoring [refactoring]
Summary: Rename published method refactoring [refactoring]
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-05-13 19:19 EDT by Jason Yip CLA
Modified: 2009-08-30 02:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Yip CLA 2003-05-13 19:19:01 EDT
Essentially Rename Method for framework/libraries.  Can't just do a normal 
Rename Method because there may be external dependencies on the old method name.

public void oldName() {}

should become

public Object newName() { ... }

/**
 * @deprecated
 */
public Object oldName() {
  return newName();
}

Obviously there are also more sophisticated scenarios with signature changes 
and package changes if renaming classes, etc.
Comment 1 Dirk Baeumer CLA 2003-05-15 17:47:20 EDT
Good suggestion.
Comment 2 Adam Kiezun CLA 2003-05-16 05:44:17 EDT
an external contribution would be much appreciated here
Comment 3 Denis Roy CLA 2009-08-30 02:20:58 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.