-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 3.1.0
-
Component/s: Maven plugin
-
None
This happens either if no java class was found for instrumentation or if they were all excluded.
Clover then reports a negative coverage of -100%.
To my mind, this is not correct : strictly speaking, if no java class has to be tested for coverage, there is no relevant coverage value (I guess it is what the -100% means) but check should be OK.
- links to