- Added a quick usage guide in the documentation.
- Fixed issue where <code>clover:report</code> was not calling <code>clover:on</code> leading to an error when generating the reports. - Ensure that <code>clover:init</code>, <code>clover:on</code> and <code>clover:off</code> can only be called once. For example calling <code>clover:on</code> twice in a row will execute it only once. - The <code>clover:*-report</code> goals do not call <code>clover:test</code> anymore. They only generates Clover reports. This is now aligned with the <code>clover:report</code> behavior. To run the full thing, execute the <code>clover</code> goal or add the Clover report to your project's POM. - Added a <code>maven.clover.multiproject</code> 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 <code>clover</code> goal and the <code>maven-clover-plugin</code> report in your POM execute on all subprojects (they'll call the new <code>clover:multiproject</code> goal). - New <code>clover:multiproject</code> goal to run Clover on a multiproject setup. - New <code>clover:merge</code> goal that creates a new Clover database by merging several other databases specified using the <code>maven.clover.merge.databases</code> property (which defaults to <code>**/clover_coverage.db</code>). git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@169652 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
@@ -26,6 +26,44 @@
|
||||
</properties>
|
||||
<body>
|
||||
<release version="1.9-SNAPSHOT" date="in SVN">
|
||||
<action dev="vmassol" type="add">
|
||||
Added a quick usage guide in the documentation.
|
||||
</action>
|
||||
<action dev="vmassol" type="fix">
|
||||
Fixed issue where <code>clover:report</code> was not calling
|
||||
<code>clover:on</code> leading to an error when generating the
|
||||
reports.
|
||||
</action>
|
||||
<action dev="vmassol" type="update">
|
||||
Ensure that <code>clover:init</code>, <code>clover:on</code>
|
||||
and <code>clover:off</code> can only be called once. For example
|
||||
calling <code>clover:on</code> twice in a row will execute it only
|
||||
once.
|
||||
</action>
|
||||
<action dev="vmassol" type="update">
|
||||
The <code>clover:*-report</code> goals do not call
|
||||
<code>clover:test</code> anymore. They only generates Clover reports.
|
||||
This is now aligned with the <code>clover:report</code> behavior.
|
||||
To run the full thing, execute the <code>clover</code> goal or
|
||||
add the Clover report to your project's POM.
|
||||
</action>
|
||||
<action dev="vmassol" type="add">
|
||||
Added a <code>maven.clover.multiproject</code> 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 <code>clover</code> goal and the
|
||||
<code>maven-clover-plugin</code> report in your POM execute on all
|
||||
subprojects (they'll call the new <code>clover:multiproject</code> goal).
|
||||
</action>
|
||||
<action dev="vmassol" type="add">
|
||||
New <code>clover:multiproject</code> goal to run Clover on a
|
||||
multiproject setup.
|
||||
</action>
|
||||
<action dev="vmassol" type="add">
|
||||
New <code>clover:merge</code> goal that creates a new Clover
|
||||
database by merging several other databases specified using
|
||||
the <code>maven.clover.merge.databases</code> property (which
|
||||
defaults to <code>**/clover_coverage.db</code>).
|
||||
</action>
|
||||
<action dev="vmassol" type="fix">
|
||||
Fixed issue with Clover task and type definitions not using an
|
||||
explicit classpath which apparently breaks under Maven 1.1.
|
||||
|
||||
Reference in New Issue
Block a user