Full name:
com.atlassian.maven.plugins:maven-clover2-plugin:2.3.1:aggregate
Description:
Aggregate children module Clover databases if there are any. This mojo should not exist. It's only there because the site plugin doesn't handle @aggregators properly at the moment...
Attributes:
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
. Default value is: ${project.build.directory}/clover/clover.db . |
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 . |
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 . |
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.String
No
${maven.clover.cloverDatabase}
${project.build.directory}/clover/clover.db
The location of the merged clover database to create when running a report in a multimodule build.
java.lang.String
Yes
${maven.clover.cloverMergeDatabase}
${project.build.directory}/clover/cloverMerge.db
When the Clover Flush Policy is set to "interval" or threaded this value is the minimum period between flush operations (in milliseconds).
int
No
${maven.clover.flushInterval}
500
The Clover flush
policy
to use. Valid values are directed
,
interval
and threaded
.
java.lang.String
No
${maven.clover.flushPolicy}
threaded
jdk :
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.String
No
${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.String
No
${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.String
No
${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.MavenProject
Yes
${project}
skip :
A flag to indicate not to run clover for this execution. If set to true, Clover will not be run.
boolean
No
${maven.clover.skip}
false
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.
boolean
No
${maven.clover.waitForFlush}
true