This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 172922 - Refactor Rename ClassName secondary use case
Summary: Refactor Rename ClassName secondary use case
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Becicka
Depends on:
Reported: 2009-09-23 17:32 UTC by sandi_ro
Modified: 2010-09-23 08:48 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description sandi_ro 2009-09-23 17:32:57 UTC
Hi , 

Please classify . 

When invoking Refactor->Rename on a class name in a definition of a member (field or method ) we actually want to change
the definition of that member . Refactor will try to change as much as possible affected code. 

i.e : 

private String foo;

public String getFoo(){
          return foo;

invoking refactor rename on String before foo field and enter Integer will change to: 

private Integer foo;

public Integer getFoo(){
          return foo;

an idea would be to let the user choose between actual rename ( changing the class name ) and behavior described here. 

Comment 1 Vojtech Sigler 2009-09-24 12:20:54 UTC
Reassigning to refactoring for evaluation.