Bug 105893 - [refactoring] Safe Delete Refactoring
Summary: [refactoring] Safe Delete Refactoring
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: All All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 118022 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-03 04:27 EDT by Leif Hanack CLA
Modified: 2011-11-08 18:15 EST (History)
6 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 Leif Hanack CLA 2005-08-03 04:27:56 EDT 
it would be a great enhancement if a safe delete of classes/methods/fields is
supported.

this refactoring is useful in cases where you need to remove a
class/method/field and check whether it is used. 

more details could be found here: 
http://www.jetbrains.com/idea/docs/help/refactoring/safedelete.html
Comment 1 Martin Aeschlimann CLA 2005-11-28 03:49:56 EST 
*** Bug 118022 has been marked as a duplicate of this bug. ***
Comment 2 Ankur Sharma CLA 2011-07-24 14:37:50 EDT 
This enhancement will make the refactoring the designs a lot easier and safer.
Comment 3 Dani Megert CLA 2011-07-25 02:57:53 EDT 
(In reply to comment #2)
> This enhancement will make the refactoring the designs a lot easier and safer.

Only if the member isn't API and only of you are 100% sure that you have all existing client code in your workspace. Otherwise it gives you false hope.
Comment 4 Thomas Singer CLA 2011-07-25 08:57:58 EDT 
(In reply to comment #3)
> Only if the member isn't API and only of you are 100% sure that you have all
> existing client code in your workspace. Otherwise it gives you false hope.

Please understand that there are people outside which use Eclipse for their own projects. Not everybody develops libraries. Not everybody makes use of reflection - there should be people which avoid reflection to get reliable find usage results.
Comment 5 Dani Megert CLA 2011-07-25 09:36:45 EDT 
(In reply to comment #4)
> (In reply to comment #3)
> > Only if the member isn't API and only of you are 100% sure that you have all
> > existing client code in your workspace. Otherwise it gives you false hope.
> 
> Please understand that
I do. I'm not saying it's not useful - just wanted to put the "safe" into the right perspective.