Clover-for-Maven 2 Changelog

Added by Rosie Jameson, last edited by Edwin Dawson [Atlassian] on Nov 05, 2008  (view change) show comment
All Versions
Click for all versions
Clover 2.4 Documentation

Index

See also Clover-for-Ant Changelog

Clover-for-Maven 2 Changelog 

The complete combined changes are as follows:

Changes in the Clover 2.4 for Maven 2 plugin

5 November, 2008

The Clover 2.4 for Maven 2 plugin is a major release which adds a key new feature, Test Optimization along with numerous improvements and bug fixes.

Issue key Summary
CLMVN-61 Add span support for clover2:aggregate task
CLMVN-43 Clover Maven Plugin broken under Maven 2.0.9
CLMVN-3 Projects fails with classes in the default package
CLMVN-14 Allow custom contexts
CLMVN-15 Allow span specification
CLMVN-37 Clover report generation is skipped when using the clean goal if <includes> are specified
CLMVN-72 PDF reports unable to be produced
CLMVN-77 Generate an XML report by default
CLMVN-76 clover2:check fails if history dir does not exist.
CLMVN-60 Add support for -Dmaven.clover.span
CLMVN-68 Aggregate reports getting incorrect test sources
CLMVN-75 Better handling of generated sources
CLMVN-79 Span attribute now defaults to "forever", instead of 0 - i.e. last compilation event
CLMVN-81 Fix eval license message
CLMVN-80 Add ability to define alwaysRunTests for build optimization
CLMVN-70 Plugin Ignoring Dependency exclusions
CLMVN-73 Surefire test runner optimizer
CLMVN-83 Preserve order of dependent artifacts when adding clover to the classpath
CLMVN-63 Deploy a relocation pom for maven-clover-plugin 3.8
CLMVN-73 Document Maven Test Optimization integration
CLMVN-21 Inner classes of test classes are shown under the 'Classes' tab instead of the 'Tests' tab in reports
CLMVN-67 Clover license being deleted in Windows.

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.

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.

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.

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.

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.

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.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.