I'm unable to download the Raw Archive of prior
posts, so If this has already been duplicated, my apologies in
advance.
I've downloaded the new Version 632 and started
running it and discovered that renaming refactoring for a instance
variable
finds all other instance
variables with the same name regardless of scoped visibility and attempts to
change all instances.
The code below shows the problem.
Class1.java
package
a;
public
class Class1 {
String env =
"class1";
.....
}
Class2.java
package
a;
public
class Class2 {
String env =
"class2";
.....
}
Attempting to rename the variable env in Class1 also
picks up and attempts to change the reference in Class2 even though
the variable in
Class2 is a totally separate variable.
Hope this is specific enough to help quickly.
-Eric.
This communication is intended only for the use of the individual or entity to whom/which it is addressed, and information contained in this communication is privileged and confidential. If the receiver of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender of this email (so that we may correct our internal records) and delete this communication without making a copy of it.
Thank you.
