Clover-for-Maven 2 Changelog

Added by Edwin Dawson [Atlassian], last edited by Edwin Dawson [Atlassian] on Apr 09, 2008
Clover 2.1 Documentation

Index

See also Clover-for-Ant Changelog

Clover-for-Maven 2 Changelog 

The complete combined changes are as follows:

Changes in the maven-clover-plugin version 3.7

27 February, 2008

The maven-clover-plugin 3.7 brings support for Maven 2 along with some Clover 2.1 features — including merging of test data and aggregated test results.

Read the documentation for instructions on how to install or upgrade. Note that a full clean build is required.

Changes in the maven-clover-plugin version 3.6

05 December, 2007

Maven-clover-plugin 3.6 includes these bug fixes and enhancements.

If you want the test results in the Clover report to come from the surefire test result files, instead of from Clover's own instrumentation:

<useSurefireTestResults>true</useSurefireTestResults>

This flag defaults to false - you only need to set this if Clover is not correctly determining the test results. See CLOV-90 for a case where this might happen.

Surefire usage is no longer supported, from maven-clover-plugin 4.0 onwards.

Changes in the maven-clover-plugin version 3.3

01 November, 2007

This release updates the version of Clover used to 2.0.2.

Clover 2.0.2 includes these bug fixes and enhancements.

In order to specify that Clover should not use a fully qualified package name when referring to classes in the java.lang package, add the following to the maven-clover-plugin configuration section of your pom:

<useFullyQualifiedJavaLang>false</useFullyQualifiedJavaLang>

This flag defaults to true - you only need to set this if you have a local variable named java.

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.