Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319916 - [refactoring] Renaming a field leads to compilation error due to hiding
Summary: [refactoring] Renaming a field leads to compilation error due to hiding
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-14 16:26 EDT by Gustavo Soares CLA
Modified: 2020-03-05 16:41 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Soares CLA 2010-07-14 16:26:59 EDT
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.
Comment 1 Eclipse Genie CLA 2020-03-05 16:41:24 EST
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.