Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368917 - [refactoring] Java IDE should provide a "Delete method along with all implementations" refactoring
Summary: [refactoring] Java IDE should provide a "Delete method along with all impleme...
Status: CLOSED DUPLICATE of bug 25097
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 03:48 EST by Tobias Gierke CLA
Modified: 2012-01-18 04:34 EST (History)
2 users (show)

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 Tobias Gierke CLA 2012-01-18 03:48:43 EST 
Build Identifier: 20110615-0604

When cleaning up code and I often need to delete unused methods. Deleting a method using the outline just deletes the current implementation/definition without affecting subclasses/implementing types.

A hack for deleting concrete methods (shamelessly stolen from http://stackoverflow.com/questions/4700015/i-cant-delete-a-method-using-eclipse-refactoring) is to perform the "Inline method" refactoring after deleting the method body manually - but this does not work for abstract methods since inlining those obviously is not possible.

Since the "Change method signature" refactoring is already able to locate all call sites for a given method, implementing this should not be too hard (i guess).

Reproducible: Always
Comment 1 Ayushman Jain CLA 2012-01-18 04:29:35 EST 
Moving to JDT/UI.
Comment 2 Dani Megert CLA 2012-01-18 04:34:57 EST 

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