Renaming fields causes conflicts with variable naming, resulting in changes in code behavior

[provide a description of the issue]

Environment

• Operating System:
• JDK version:
• Visual Studio Code version:
• Java extension version:

Steps To Reproduce

1.select "originalField"
2.click “Rename”
3. new name "originalFieldRenamed"

class MyClass {
// rename "originalField" to "originalFieldRenamed"
private final int originalField = 10;
protected int protectedField;

public void myMethod() {
int originalFieldRenamed = 20; // Local variable with the same name as the field
System.out.println(originalField);
}
}
refactoring result:

Start by reproducing the listed rename steps in the Java example and compare the resulting references with the intended field rename. Trace the Java rename-refactoring path to identify why a local variable with the new field name changes behavior; done means the rename preserves the local variable and field semantics for this example.