Currently if a subclass concretely overrides an abstract method of its parent class and its method documentation is as

/**
 * {@inheritDoc}
 */

then the subclass method's javadoc will end up in the "Methods declared in class packageName.superclassName" section of the subclass javadoc instead of in the primary method listing. In this case the only way to know that the class overrode the method is to note that the class is concrete whereas its parent class is abstract. If there are several abstract classes in a hierarchy it can be impossible to determine which class overrode the method. Knowing which class(es) actually implement(s) the abstract method may be information valuable to a developer.

In general it would be good if inheritDoc were to automatically generate verbiage for an overriding method for changes in abstractness, access modifiers (protected to public), finality (non-final to final), and any other appropriate user-visible method signature changes.