Summary: | [refactoring] [rename] Renaming not cascadable. | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Wynne Crisman <wcrisman> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | daniel_megert, markus.kell.r, mn, pwebster |
Version: | 3.4.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Wynne Crisman
2008-11-08 15:40:21 EST
Markus, please comment. Cascaded refactorings are currently not supported by the processor/participant infrastructure. The framework would need to make sure that cascaded refactorings don't end up in loops. I agree that this would be nice, but it would be a lot of work to implement, and we unfortunately don't have the resources to do this at the moment. The best advice I can give you right now is to do it asynchronously, i.e. schedule a Job in your participant which calls the RenameSupport API to trigger rename of the Java file after X has been renamed. |