Description David Witherspoon 2010-05-12 08:54:30 EDT

Build Identifier: 20090920-1017

If I attempt to rename a method like  getID() to getId() [note the little 'd'], if some affected files are read-only, the refactor will silently fail.  The key here is that the new method name equalsIgnoreCase the old name.

If I attempt to rename the same method to getIdddd(), I will get warnings that some affected files are read-only, and an option to make them writable.

Reproducible: Always

Steps to Reproduce:
Create classes:
     class Foo { 
        public static void getID() {;} 
     }
     class FooUser {  // ensure this file is read-only
        public causeTrouble() {
           Foo.getID();
        }
     }

Refactor Foo, renaming getID to getId (little d).  Even though FooUser is read-only, it'll fail to recognize and will silently fail.  Now rename getID to getIdddddd, and you'll get the warning that FooUser is read-only.