Bug 38648 - Rename method arguments also renames parent class/interface arguments [refactoring]
Summary: Rename method arguments also renames parent class/interface arguments [refact...
Status: ASSIGNED
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: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-09 10:01 EDT by Channing Walton CLA
Modified: 2003-06-10 19:54 EDT (History)
1 user (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 Channing Walton CLA 2003-06-09 10:01:24 EDT 
If I refactor (rename) a method argument, I would like to have the argument
renamed in the interface or super class that the method was defined in as well.

If there is more than one super class or interface that define the method
argument, then the user can choose which to change from a list.

Channing
Comment 1 Dirk Baeumer CLA 2003-06-10 05:12:07 EDT 
Adam, 

any reason why we don't do it ?
Comment 2 Adam Kiezun CLA 2003-06-10 19:54:36 EDT 
method parameter names are independent from each other so in every 
implementation there can be a different set of problems caused by renamings

but i guess this can be improved with no so much effort, i'll see