When your development team is divided in groups that owns different components and these components interact through public APIs, refactoring the APIs might require multiple-steps. Ideally everybody would own the code so if you rename an API method you can rename all its usages whether they are owned by you or not. However when you do not have control over all user components the current refactoring tool doesn't help. You need to save your refactoring into a refactoring batch file that can be applied to user components when they migrate to your new release. You can then release the refactoring file with the new interface. Users can apply the refactorings on their code.
Jacques Morel _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
