diff --git a/clover/project.xml b/clover/project.xml index 25e5ec07..cb262f7f 100644 --- a/clover/project.xml +++ b/clover/project.xml @@ -23,7 +23,7 @@ 3 maven-clover-plugin Maven Clover Plugin - 1.9-SNAPSHOT + 1.9 The Clover plugin allows measuring test coverage using Clover (http://www.cenqua.com/clover). Produce Clover reports http://maven.apache.org/reference/plugins/clover/ @@ -65,6 +65,11 @@ 1.8 MAVEN_CLOVER_1_8 + + 1.9 + 1.9 + MAVEN_CLOVER_1_9 + diff --git a/clover/xdocs/changes.xml b/clover/xdocs/changes.xml index b02e478e..6a5b0fb1 100644 --- a/clover/xdocs/changes.xml +++ b/clover/xdocs/changes.xml @@ -25,73 +25,53 @@ Emmanuel Venisse - + - maven.test.failure.ignore is now correctly reset - when clover:off is called. + maven.test.failure.ignoreis now correctly reset when + clover:offis called. - - Fully disable Clover in clover:off so that the Clover - compiler adapter delegates straight to the default compiler. + Fully disable Clover in + clover:offso that the Clover compiler adapter delegates straight to the default compiler. - - Removed the maven.clover.jar property that was used to - override the default Clover jar. This property was not working - (it requires Ant 1.6) and is no needed anymore as Cenqua has cleanly - separated the Clover jar from the Clover license. You only need to - point maven.clover.license.path to your license file. + Removed the + maven.clover.jarproperty that was used to override the default Clover jar. This property was not working (it requires Ant 1.6) and is no needed anymore as Cenqua has cleanly separated the Clover jar from the Clover license. You only need to point + maven.clover.license.pathto your license file. - - Added a quick usage guide in the documentation. + Added a quick usage guide in the documentation. + Fixed issue where + clover:reportwas not calling + clover:onleading to an error when generating the reports. - - Fixed issue where clover:report was not calling - clover:on leading to an error when generating the - reports. + Ensure that + clover:init, + clover:onand + clover:offcan only be called once. For example calling + clover:ontwice in a row will execute it only once. - - Ensure that clover:init, clover:on - and clover:off can only be called once. For example - calling clover:on twice in a row will execute it only - once. + The + clover:*-reportgoals do not call + clover:testanymore. They only generates Clover reports. This is now aligned with the + clover:reportbehavior. To run the full thing, execute the + clovergoal or add the Clover report to your project's POM. - - The clover:*-report goals do not call - clover:test anymore. They only generates Clover reports. - This is now aligned with the clover:report behavior. - To run the full thing, execute the clover goal or - add the Clover report to your project's POM. + Added a + maven.clover.multiprojectproperty that should be set to true in your master project (if you're using a multiproject setup). Setting it to true will make the + clovergoal and the + maven-clover-pluginreport in your POM execute on all subprojects (they'll call the new + clover:multiprojectgoal). - - Added a maven.clover.multiproject property that should be - set to true in your master project (if you're using a multiproject setup). - Setting it to true will make the clover goal and the - maven-clover-plugin report in your POM execute on all - subprojects (they'll call the new clover:multiproject goal). + New + clover:multiprojectgoal to run Clover on a multiproject setup. - - New clover:multiproject goal to run Clover on a - multiproject setup. - - - New clover:merge goal that creates a new Clover - database by merging several other databases specified using - the maven.clover.merge.databases property (which - defaults to **/clover_coverage.db). - - - Fixed issue with Clover task and type definitions not using an - explicit classpath which apparently breaks under Maven 1.1. - - - Always generate Clover reports even when there is no coverage data. One - of the reason is that Clover generates metrics other than coverage - percentage, like LOC and NCLOC which are useful in themselves. + New + clover:mergegoal that creates a new Clover database by merging several other databases specified using the + maven.clover.merge.databasesproperty (which defaults to + **/clover_coverage.db). + Fixed issue with Clover task and type definitions not using an explicit classpath which apparently breaks under Maven 1.1. + Always generate Clover reports even when there is no coverage data. One of the reason is that Clover generates metrics other than coverage percentage, like LOC and NCLOC which are useful in themselves. Upgraded to Clover 1.3.6 - - Added PDF report generation. - + Added PDF report generation. Added support for historical reports by adding a new