Renaming fields causes conflicts with parameter 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 AnotherClass {
// rename originalFieldRenamed
int originalField = 20;

public void anotherMethod(int originalFieldRenamed) {
int localVar = originalFieldRenamed; // Local variable with the same name as the field
System.out.println(originalField);
}
}

refactoring result:

No source file or test is named. Start by reproducing the rename steps in the Java snippet, then inspect the refactoring entry point that handles field and parameter name conflicts. Done means renaming originalField preserves the intended field and local-variable references without changing behavior.