See also Clover-for-Ant Changelog
Clover-for-Maven 2 Changelog
- Changes in 2.4.3 for Maven 2
- Changes in 2.3.2 for Maven 2
- Changes in 2.3.0 for Maven 2
- Changes in 2.5.0 for Maven 2
- Changes in 2.02 for Maven 2 (plugin version 3.6)
- Changes in 2.1 for Maven 2 (plugin version 3.7)
- Changes in 2.4.2 for Maven 2
- Changes in 2.4.0 for Maven 2
- Changes in 2.0.2 for Maven 2 (plugin version 3.3)
The complete combined changes are as follows:
Changes in the Clover 2.5.0 for Maven 2 plugin
11 May, 2009
Clover 2.5.0 for Maven 2 is a major release which adds support for Test Optimization.
新機能
課題キー |
要約 |
|---|---|
Make maven properties available to custom report descriptors. |
|
Support for distributed per-test coverage. |
|
Add a forceSnapshot configuration option. |
改善点
課題キー |
要約 |
|---|---|
Don't add too many dependencies when swizzling artifacts. |
|
Don't optimize if both src/main and src/test are missing. |
|
Honor Maven's global setting for source file encoding. |
バグ修正
課題キー |
要約 |
|---|---|
Artifacts with the same name (but different groupIds) being resolved incorrectly. |
|
Test run in different module does not update coverage. |
|
clover2:merge goal does not setup the licensing correctly. |
Atlassian recognizes Henri Tremblay, who submitted a patch for Clover-for-Maven 2, which was reviewed and integrated into the product.
Changes in the Clover 2.4 for Maven 2 plugin
2008 年 11 月 5 日
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.
課題キー |
要約 |
|---|---|
Add span support for clover2:aggregate task |
|
Clover Maven Plugin broken under Maven 2.0.9 |
|
Projects fails with classes in the default package |
|
Allow custom contexts |
|
Allow span specification |
|
Clover report generation is skipped when using the clean goal if <includes> are specified |
|
PDF reports unable to be produced |
|
Generate an XML report by default |
|
clover2:check fails if history dir does not exist. |
|
Add support for -Dmaven.clover.span |
|
Aggregate reports getting incorrect test sources |
|
Better handling of generated sources |
|
Span attribute now defaults to "forever", instead of 0 - i.e. last compilation event |
|
Fix eval license message |
|
Add ability to define alwaysRunTests for build optimization |
|
Plugin Ignoring Dependency exclusions |
|
Surefire test runner optimizer |
|
Preserve order of dependent artifacts when adding clover to the classpath |
|
Deploy a relocation pom for maven-clover-plugin 3.8 |
|
Document Maven Test Optimization integration |
|
Inner classes of test classes are shown under the 'Classes' tab instead of the 'Tests' tab in reports |
|
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.
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.
新機能
課題キー |
要約 |
|---|---|
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. |
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
2007 年 11 月 01 日
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.