Nathan,
I believe this is fixed in #635. If you typed in a class name
in "Change Method Signature" dialog and this class was resolvable
in where the method is, refactoring behaves correctly (that is,
neccessary import statements are inserted in classes
overriding/implementing this method).
Friendly,
Dmitry
Nathan Brown wrote:
> I'm not sure if other refactoring is affected by this, but the one I
> just noticed it on is 'Change Method Signature'. I changed a parameter
> type of a fundamental interface (80 implementations) and now I have 80
> 'cannot resolve symbol' errors when I compile.
>
> It would be brilliant if IDEA could have asked me exactly what type I
> was changing it to and ensured that the new parameter type is imported
> in all classes where the method is implemented.
>
> N.
>
--
Dmitry Lomov
JetBrains Inc. / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-features
