Bug 152168 - Rename field refactoring should propose rename parameter on setter and constructor
Summary: Rename field refactoring should propose rename parameter on setter and constr...
Status: RESOLVED DUPLICATE of bug 64698
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-28 12:18 EDT by Willian Mitsuda CLA
Modified: 2006-08-02 13:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Willian Mitsuda CLA 2006-07-28 12:18:33 EDT
If I have a code like:

public class FooClass {

    private int foo;

    public FooClass(int foo) {
        this.foo = foo;
    }

    public int getFoo() {
        return foo;
    }

    public void setFoo(int foo) {
        this.foo = foo;
    }

}

If I execute a rename field refactoring on "foo" attribute to, let's say, "bar", it proposes to rename "getFoo()" to "getBar" and "setFoo" to "setBar".

It should also propose to rename the "int foo" parameter to "int bar" in setter and constructor.
Comment 1 Maxime Daniel CLA 2006-07-31 02:58:14 EDT
Moving to JDT UI.
Comment 2 Martin Aeschlimann CLA 2006-08-02 13:10:01 EDT

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