Skip to end of metadata
Go to start of metadata
All Versions
Clover 2.3 Documentation

See also Clover-for-Ant Changelog

Clover-for-Maven 2 Changelog 

The complete combined changes are as follows:

Changes in the Clover 2.3.2 for Maven 2 plugin

15 July, 2008

The Clover 2.3.2 for Maven 2 plugin is a bug fix and minor feature release.

Issue key

Summary

CLMVN-36

Maven clover plugin should support merging arbitrary number of clover databases, not just one

CLMVN-47

Set the encoding of HTML reports

CLMVN-64

Allow custom report descriptor to be specified on the classpath, like clover.license

Changes in the Clover 2.3.0 for Maven 2 plugin

12 June, 2008

The Clover 2.3.0 for Maven 2 plugin adds a number of improvements and bug fixes.

Icon

Upgrading the Maven 2 plugin
There are specific steps required for upgrading from a previous version of the plugin: see the Upgrade Guide for details.

(info) New version numbering and Maven Artifact ID
In changing the Artifact ID of this project to maven-clover2-plugin, the Clover team has taken the opportunity to bring the version numbering into sync with Clover-for-Ant. This is to make version numbers of Clover for various platforms better reflect the feature set, so that all Clover releases with a given version number will be largely the same.

New Features

Issue key

Summary

CLMVN-35

Enable clover-check to use historydir parameter when checking coverage.

Improvements

Issue key

Summary

CLMVN-17

Ability to disable the plugin for one or more modules in a multi-module build.

CLMVN-27

Generate and Publish the Maven Clover plugin's site.

CLMVN-38

Document the removal of useSureFiretestResults configuration.

CLMVN-41

Investigate Maven Multi-Module problem.

Bug Fixes

Issue key

Summary

CLMVN-29

Make historyDir multi-module aware.

CLMVN-32

Instrumented and uninstrumented jar are on the runtime classpath

CLMVN-25

Clover reports don't work for cross module tests

CLMVN-42

Unable to instrument tests named using Japanese characters.

CLMVN-44

Illegal Char in path on Windows.

Upgrade Considerations for this release of Clover-for-Maven 2

1. Method name prefixes

Methods beginning with 'generate'are now in the maven.clover namespace. This means that the following properties must have the prefix 'maven.clover' added to them. This is an issue for backwards compatibility.

The change make these properties more consistent with all other properties, as well as making them safer to use with other plugins.

2. 'Clover:' must be expressed as 'Clover2:'

Wherever 'Clover:' is used, you must change it to 'Clover2:' to take advantage of the new version.

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.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.

com.atlassian.confluence.macro.MacroExecutionException: java.lang.RuntimeException: Not Found

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.

com.atlassian.confluence.macro.MacroExecutionException: java.lang.RuntimeException: Not Found

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:

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.

Icon

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.

Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

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:

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


  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

 

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.