Jason Yip points to a cool new refactoring feature in Eclipse 3.2 M5. For reference, the refactoring support in Eclipse already handles all of the messiness associated with renaming a method- updating references to the method, updating your comments, etc. However, that was all for the references inside your own codebase. It now can keep the old method name around as a pointer to the new method name. This gives you the ability to broadcast the change to any external consumers of that method via a deprecation warning- letting them know not to depend on the existence of that method for much longer, while still allowing you to keep the code in just one place. Don't repeat yourself!
Now, am I going to mess around with upgrading to a development version of Eclipse to get this? Might be too risky at the current juncture. I am going to have to check out the buglist.