| Extending the Rename Refactoring [message #250593] |
Fri, 11 January 2008 13:18 |
Eclipse User |
|
|
|
Originally posted by: myawn.ebay.com
I'm looking at writing a Refactoring Participant (for the rename
refactoring) to handle modifications to our generated code.
Some of the extensions are obviously customized for our specific setup
-- changing members of Enums, setting some constant values, etc.
But some of what we're looking at is very standard Java (or so it
seems), so I'm wondering if there is some design reason why the existing
refactorings don't include this.
We have a setup where there is an interface that has get and set methods
for various properties, as well as an implementor of the interface that
implements the get and set and has a member variable to contain the
property value.
If I refactor/rename the get method in the interface, there is no
automated update of the property in the implementation class or the set
method.
Is it generally thought that having the refactoring do this is :
- a bad idea, and if so why
- a good idea, but difficult to do and thus unimplemented
Thanks
Mike
|
|
|
Powered by
FUDForum. Page generated in 0.04833 seconds
Home