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.
| Summary: | Refactor Rename ClassName secondary use case | ||
|---|---|---|---|
| Product: | java | Reporter: | sandi_ro <sandi_ro> |
| Component: | Refactoring | Assignee: | Jan Becicka <jbecicka> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Reassigning to refactoring for evaluation. |
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. Thanks.