Abstract_Class_Added_Super_Interface thrown when not appropriate

[chuckleslord]

I'm having dual unnecessary instances of Abstract_Class_Added_Super_Interface being thrown.

The first reason why it's unnecessary is that all of the methods in my interface are Java 8 default methods. Meaning that there will never be a case where a child class will get an Unimplemented Abstract Method error.

And the second reason is that this error is unnecessary is because the class I added the implementation to already has all of the implementations methods overwritten. Therefore, there is, again, no way for the child to need to worry about overwriting it.

Are my expectations of this utility missing the mark or are these actually in error?

[RyanSkraba]

I believe this can be reproduced by adding the java.io.Serializable interface to an abstract class. There are no new methods to be implemented, but a High source compatibility break is noted.