“Pull Down Field” refactoring caused a change in the code behavior

Code before refactoring:
```java
class A extends C {
}

class B {
void main() {
final int b = 2;
new A() {
void m() {
System.out.println(b);
}
};
}
}
class C {
protected final int b = 1;
}
```
Code after refactoring:
```java
class A extends C {
protected final int b = 1;
}

class B {
void main() {
final int b = 2;
new A() {
void m() {
System.out.println(b);
}
};
}
}
class C {
}
```
The output before code refactoring is 1, and the output after refactoring is 2. The code behavior has changed.

Reproduce the reported example with Eclipse JDT UI's “Pull Down Field” refactoring and compare the output before and after. Start at the Pull Down Field refactoring entry point and verify that the anonymous subclass still resolves the field as 1 after refactoring; done means the refactoring preserves the original behavior.

Written by the indexing model from the issue text.