Changing the access level of a wireframe class / method

Question

In this example, AbstractAnimal has many out-of-scope implementations. However, this structure is being reorganized so that WalkingAnimals now exist. He suggested that Dog, among all other animals, now inherits WalkingAnimal. For example, there are no animals that do not walk. All heirs must be reorganized.

This is a Java structure, so I will refer to it as such. But feel free to interpret this question more generally. Since it is large enough, we would like our IDE to provide some indication that the classes that currently inherit AbstractAnimal should be changed. So we thought about @Deprecated annotations. However, the framework itself will issue warnings, so it should not be the cleanest method.

In fact, there are classes and methods whose access level will change, so that only the structure can use it. We would like to announce this in the classes to be refactored as much as possible (e.g. warnings and strikethroughs provided by @Deprecated). Our IDE is IntelliJ IDEA, and we work with Java 1.8.

We are looking for some kind of automatic task creation in the sense that developers can look at the list of alerts and find out what else they need to change. Also, the bossman would like progress to be achieved, so making this counting account will be a big plus.

Thank you in advance for any advice.

Answer 1

What you can do is add an abstract mannequin method to AbstractAnimal, called youShouldNotExtendAbstractAnimalDirectly(), which only has an implementation in WalkingAnimal. This will cause compilation to fail Dog, and when developers try to fix it, they will stumble on this method and either take a hint or start shooting in the leg.

Answer 2

walk AbstractAnimal, OperationNotSupportedException.

public void walk() {
    throw new OperationNotSupportedException();
}

, .

EDIT: , , , . , ; , .