We are switching off article comments on this website. Read about the upcoming changes to Atlassian Documentation.
12 June, 2008
The Clover 2.3.0 for Maven 2 plugin adds a number of improvements and bug fixes.
Upgrading the Maven 2 plugin
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.
Enable clover-check to use historydir parameter when checking coverage.
Ability to disable the plugin for one or more modules in a multi-module build.
Generate and Publish the Maven Clover plugin's site.
Document the removal of useSureFiretestResults configuration.
Investigate Maven Multi-Module problem.
Make historyDir multi-module aware.
Instrumented and uninstrumented jar are on the runtime classpath
Clover reports don't work for cross module tests
Unable to instrument tests named using Japanese characters.
Illegal Char in path on Windows.
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.
maven.clover.generateHtml maven.clover.generatePdf maven.clover.generateXml maven.clover.generateJson maven.clover.generateHistorical maven.clover.orderBy
The change make these properties more consistent with all other properties, as well as making them safer to use with other plugins.
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.