I tried to come up with a simple detailed example that demonstrated this problem, but I could not reproduce the problem. I did encounter this bug yesterday with my project, which is large and complex and something I cannot send to you. But it did happen ... I guess I will just be careful when renaming and if I come up with a repeatable test case, contact you again.
Phil Valentin Kipiatkov wrote: > Could you please provide more detailed example? Your example does not > contain any usages that might be renamed. > > Best regards, > Valentin Kipiatkov > ----------------------------------------------------------- > IntelliJ Software, http://www.intellij.com/ > "Develop with pleasure" > ----------------------------------------------------------- > > ----- Original Message ----- > From: "Philip Miller" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 25, 2002 5:46 PM > Subject: [Eap-list] bug in refactor rename > > > I just tried to rename a static inner class named Gui and the rename > > refactoring tried to rename references to another package's Gui class. > > Here is a sample where renaming a.Foo.Gui resulted with b.Gui also > > getting renamed. > > > > package a; > > > > class Foo { > > public static class Gui { > > } > > } > > > > > > package b; > > public class Gui { > > } > > > > > > Thanks for your help. > > > > Phil > > > > > > _______________________________________________ > > Eap-list mailing list > > [EMAIL PROTECTED] > > http://www.intellij.com/mailman/listinfo/eap-list > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
