| Summary: | [refactoring] Renaming a field leads to compilation error due to hiding | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gustavo Soares <gsoares> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Build Identifier: 20090920-1017 Apply the rename method leads to field hiding. After the refactoring, a field is not visible for a field call. Reproducible: Always Steps to Reproduce: 1. Create the classes: public class A { int f; } public class B extends A{ private int n; } public class C extends B{ void m() { super.f = 1; } } 2. Apply the rename refactoring to B.n renaming it to f: public class A { int f; } public class B extends A{ private int f; } public class C extends B{ void m() { super.f = 1; } } 3. After the refactoring the field f is not visible to the expression in method m() leading to compilation error.