Overview
Examples
Architecture
Project Documentation
Full name:
com.atlassian.maven.plugins:maven-clover2-plugin:2.4.2:clean
Description:
The clover2:clean goal should be run directly from the command line, when you are developing using the clover test runner optimizer. This mojo ensures that the file required by Clover to optimize your test is not deleted between builds. Unfortunately, the implementation is not optimal. It will be a lot simpler however if the patch attached to http://jira.codehaus.org/browse/MCLEAN-38 is applied. Then, this plugin can simply set the maven.clean.excludes property.
Attributes:
initialize.| Name | Type | Since | Description |
|---|---|---|---|
| cloverMergeDatabase | String |
- |
The location of the merged clover database to create when running a
report in a multimodule build. Default value is: ${project.build.directory}/clover/cloverMerge.db. |
| project | MavenProject |
- |
The Maven project instance for the executing project.
Note: This is passed by Maven and must not be configured by the user. |
| Name | Type | Since | Description |
|---|---|---|---|
| cloverDatabase | String |
- |
The location of the Clover database . |
| flushInterval | int |
- |
When the Clover Flush Policy is set to "interval" or threaded this
value is the minimum period between flush operations (in
milliseconds). Default value is: 500. |
| flushPolicy | String |
- |
The Clover flush
policy
to use. Valid values are directed,
interval and threaded. Default value is: threaded. |
| jdk | String |
- |
Whether the Clover instrumentation should use the Clover
jdk14, jdk15 or jdk16 flags
to parse sources. Valid values are 1.4, 1.5 and 1.6 . |
| license | String |
- |
The full Clover license String to use. If supplied, this
certificate will be used over licenseLocation. NB.
newline chars must be preserved. A trial Clover license can be
generated
here
. |
| licenseLocation | String |
- |
A Clover license file to be used by the plugin. The plugin tries to resolve this parameter first as a resource, then as a URL, and then as a file location on the filesystem. A trial Clover license can be generated here . |
| singleCloverDatabase | boolean |
- |
If true, then a single cloverDatabase will be used for the entire
project. This flag will be ignored if a custom cloverDatabase
location is specified. Default value is: false. |
| skip | boolean |
- |
A flag to indicate not to run clover for this execution. If set to
true, Clover will not be run. Default value is: false. |
| snapshot | File |
- |
The location to store the clover snapshot file. This file needs to persist between builds to enable Clover's build optimization feature. If not specified, the snapshot will be stored next to the cloverDatabase. |
| snapshotPattern | String |
- |
The location of the snapshot file. By default, this is next to the cloverDatabase. |
| waitForFlush | boolean |
- |
If true we'll wait 2*flushInterval to ensure coverage data is
flushed to the Clover database before running any query on it.
Note: The only use case where you would want to turn this off is if you're running your tests in a separate JVM. In that case the coverage data will be flushed by default upon the JVM shutdown and there would be no need to wait for the data to be flushed. As we can't control whether users want to fork their tests or not, we're offering this parameter to them. Default value is:true. |
The location of the Clover database .
java.lang.StringNo${maven.clover.cloverDatabase}The location of the merged clover database to create when running a report in a multimodule build.
java.lang.StringYes${maven.clover.cloverMergeDatabase}${project.build.directory}/clover/cloverMerge.dbWhen the Clover Flush Policy is set to "interval" or threaded this value is the minimum period between flush operations (in milliseconds).
intNo${maven.clover.flushInterval}500The Clover flush
policy
to use. Valid values are directed,
interval and threaded.
java.lang.StringNo${maven.clover.flushPolicy}threadedjdk :
Whether the Clover instrumentation should use the Clover
jdk14, jdk15 or jdk16 flags
to parse sources. Valid values are 1.4, 1.5 and 1.6 .
java.lang.StringNo${maven.clover.jdk}license :
The full Clover license String to use. If supplied, this
certificate will be used over licenseLocation. NB.
newline chars must be preserved. A trial Clover license can be
generated
here
.
java.lang.StringNo${maven.clover.license}A Clover license file to be used by the plugin. The plugin tries to resolve this parameter first as a resource, then as a URL, and then as a file location on the filesystem. A trial Clover license can be generated here .
java.lang.StringNo${maven.clover.licenseLocation}project :
The Maven project instance for the executing project.
Note: This is passed by Maven and must not be configured by the user.
org.apache.maven.project.MavenProjectYes${project}If true, then a single cloverDatabase will be used for the entire project. This flag will be ignored if a custom cloverDatabase location is specified.
booleanNo${maven.clover.singleCloverDatabase}falseskip :
A flag to indicate not to run clover for this execution. If set to true, Clover will not be run.
booleanNo${maven.clover.skip}falsesnapshot :
The location to store the clover snapshot file. This file needs to persist between builds to enable Clover's build optimization feature. If not specified, the snapshot will be stored next to the cloverDatabase.
java.io.FileNo${maven.clover.snapshot}The location of the snapshot file. By default, this is next to the cloverDatabase.
java.lang.StringNo${maven.clover.snapshotPattern}If true we'll wait 2*flushInterval to ensure coverage data is flushed to the Clover database before running any query on it.
Note: The only use case where you would want to turn this off is if you're running your tests in a separate JVM. In that case the coverage data will be flushed by default upon the JVM shutdown and there would be no need to wait for the data to be flushed. As we can't control whether users want to fork their tests or not, we're offering this parameter to them.
booleanNo${maven.clover.waitForFlush}true