#7 Detect method move in class hierarchy

[Lars Kühne]

Suggestion from Stephen Colebourne via Email:

--snip--
It would be nice if the message about adding a method
referred to the
method as having moved from the old superclass. Example
for current output:

ERROR: Removed
org.apache.commons.collections.iterators.ProxyIterator from
the list of superclasses of
org.apache.commons.collections.iterators.TransformIterator
INFO: Method 'public java.util.Iterator getIterator()'
has been added in
org.apache.commons.collections.iterators.TransformIterator

The method getIterator() has been added to
TransformIterator by 'moving' it from ProxyIterator.
Using a different message in this case, eg.

INFO: Method 'public java.util.Iterator getIterator()'
has been added in
org.apache.commons.collections.iterators.TransformIterator
having previously existed in the removed superclass
org.apache.commons.collections.iterators.ProxyIterator

This then helps me to identify the reason for adding
the method to
TransformIterator.
--snip--

Additionally it would be useful to detect a "pull up in
class hierarchy" refactoring (i.e. moving methods to a
superclass).

[Lars Kühne]

Logged In: YES
user_id=401384

FYI, I'll start working on the "pull up in class hierarchy"
detection now.