Summary: | [move method][refactoring] moveParticipants doesn't work for MoveInstanceMethod | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Danny Dig <dannydig> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | daniel_megert, markus.kell.r, verawahler |
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Danny Dig
2005-02-24 02:18:08 EST
Dani, although the refactoring is implemented as a processor it doesn't currently load any participants(see method loadParticipants in MoveInstanceMethodProcessor). The refactorings that support participants are listed in the interface IRefactoringProcessorIds, which is public API. Adding this support will very likely not happen for 3.1. Our current focus is J2SE 5.0 and performance. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. I am developing the moreUnit plugin which helps user to write unit tests. There is refacotring support: if a user renames a method, the testcase gets renamed as well... I can not implement move method refactoring support for instance methods if participants are not supported. Any chance this will be added? We have no plans to work on this, but we could look into a high quality patch. But note that this will not be as easy as participant support for moving resources or static members. The Move Instance Method refactoring not only moves the method, but it also adds a parameter sometimes, so this also needs to be reflected in the refactoring arguments. |