#451 false +: AbstractClassWithoutAbstractMethod ext abstr class

[Jeff Jensen]

A declared abstract class that extends an abstract
class and has no ancestor abstract methods implemented
in it falsely triggers the
AbstractClassWithoutAbstractMethod rule.

If the declared abstract class instead implements an
interface and implements none of the interface methods,
the rule works correctly (does not trigger a false
positive).

Attached are very simple Java classes that reproduce
the false positive.

[Jeff Jensen]

Abstract classes that cause the false positive and show the interface case does not.

[Jeff Jensen]

Logged In: YES
user_id=498804

Contradicts bug #1265474 (also by me), as it said interface
case has false positive too.

[Daniel Le Berre]

Logged In: YES
user_id=969476

I got the same problem: the Abstract class implements a
subset of its base class abstract methods.

PMD thinks the abstract class has no abstract methods while
it has 2 inherited from its base class.

http://www.sat4j.org/clover/org/sat4j/minisat/constraints/AbstractCardinalityDataStructure.html#21

[Tom Copeland]

Logged In: YES
user_id=5159
Originator: NO

Assigning away from me in case someone else can look into this...
Tom