The location of the Clover database.

The difference (in milliseconds) that a -clover classified artifact can have to a non-clover classified artifact.

If the -clover classified artifact is more than cloveredArtifactExpiryInMillis older than the non-clover classified artifact, then the non-classified artifact will be used.

This setting defaults to 2000.

The location of the merged clover database to create when running a report in a multimodule build.

The directory where the Clover plugin will put all the files it generates during the build process. For example the Clover plugin will put instrumented sources somewhere inside this directory.

If set, then the clover-maven-plugin will not copy files that were excluded, across to the target/clover directory. This is useful if the build is also using plugins such as the maven-gwt-plugin, that scans for resources, and skips a step if none are found. Otherwise, setting this to false could well cause build failures.

If you wish to enable debug level logging in just the Clover plugin, set this to true. This is useful for integrating Clover into the build.

The configuration for distributed coverage collection by Clover.

If present, default values will be used and coverage will be collected across JVMs.

Optional nested elements (and their defaults) of distributedCoverage are:

• host - the host name of the JVM running the tests. default: localhost
• port - the port that Clover can bind to in the host JVM. default: 1198
• numClients - the number of clients expected to attach to the Test JVM. The test JVM will wait until numClients have connected before continuing. default: 0
• timeout - the amount of time to wait for a response from a remote JVM before shunning it. default: 5000
• retryPeriod - the amount of time a client should wait between reconnect attempts. default: 1000

The character encoding to use when parsing source files.

The list of file to exclude from the instrumentation. Patterns are resolved against source roots.

The file containing a list of file paths, separated by new line, to exclude from the instrumentation. Patterns are resolved against source roots. See also com.atlassian.maven.plugin.clover.internal.AbstractCloverInstrumentMojo.excludes and com.atlassian.maven.plugin.clover.internal.AbstractCloverInstrumentMojo.excludesList

The comma seperated list of file to exclude from the instrumentation. Patterns are resolved against source roots.

When the Clover Flush Policy is set to "interval" or threaded this value is the minimum period between flush operations (in milliseconds).

The Clover flush policy to use. Valid values are directed, interval and threaded.

By default, Clover Maven Plugin generates the ${java.io.tmpdir}/grover*.jar file during setup, which is next being added as the dependent artifact to the build. As the file has generated, unique name and the jar is not being removed at the end of the build, these files can litter the temporary directory.

By setting this parameter you can:

a) specify constant file name for generated artifact,

b) choose location different than ${java.io.tmpdir}.

However, you must ensure that:

a) grover.jar will not be deleted till end of the build (for example don't put into ./target directory and next run mvn clover:setup clean)

b) grover.jar will not be shared among builds with different Clover Maven Plugin versions used (for example if ProjectA uses Clover v 3.1.8 and ProjectB uses Clover v 3.1.9 then they shall have different groverJar locations defined)

The list of file to include in the instrumentation. Patterns are resolved against source roots. Defaults are '**/*.java, **/*.groovy' which are overwritten if <includes> is set by the user

Till 3.1.11: whether the Clover plugin should instrument all source roots (for example src/main/java, src/main/groovy, target/generated-sources, so including the generated sources) or whether it should only instrument the main source root (usually src/main/java).

Since 3.1.12: whether the Clover plugin should instrument all source roots (for example src/main/java, src/main/groovy, target/generated-sources, so including the generated sources) or whether it should instrument non-generated source roots (i.e. all roots except target/generated-sources/*)

The file containing a list of file paths, separated by new line, to include in the instrumentation. Patterns are resolved against source roots. See also com.atlassian.maven.plugin.clover.internal.AbstractCloverInstrumentMojo.includes and com.atlassian.maven.plugin.clover.internal.AbstractCloverInstrumentMojo.includesList

The comma seperated list of files to include in the instrumentation. Patterns are resolved against source roots. Defaults are **.java which are overwritten if <includes> is set by the user

Whether the Clover plugin should instrument test source roots.

The level to instrument to. Valid values are 'method' or 'statement'. Default is 'statement'.

Setting this to 'method' greatly reduces the overhead of enabling Clover, however limited or no reporting is available. The current use of setting this to method is for Test Optimization only.

Define whether lambda functions shall be instrumented: Valid values are:

• none - do not instrument lambda functions (note: statements inside lambdas will become a part of a parent function)
• expression - instrument only expression-like lambdas, e.g. (a,b) -> a + b
• block - instrument block lambdas, e.g. () -> { foo(); }
• all_but_reference - instrument lambdas written in any form except method references, e.g. Math::abs
• all - instrument all forms of lambda functions

Default is 'all' for 3.2.2-4.0.2 and 'none' since 4.0.3.

IMPORTANT: Due to Clover's restrictions related with code instrumentation and javac compiler's type inference capabilities, you may get compilation errors when expression-like lambda functions are passed to generic methods or types. In such case disable instrumentation of expression-like form (i.e. use the 'none' or 'block' setting). See the Java 8 code instrumented by Clover fails to compile Knowledge Base article for more details.

Which Java language level Clover shall use to parse sources. Valid values are:

• 1.7 (String in switch, try with resources, binary literals, underscores in literals)
• 1.8 (lambda expressions, default methods in interfaces)
• 9 / 1.9 (module-info.java)

By default Clover instruments using the highest language level supported.

The full Clover license String to use. If supplied, this certificate will be used over com.atlassian.maven.plugin.clover.internal.AbstractCloverMojo.licenseLocation. NB. newline chars must be preserved. If not provided, Clover will use a bundled license key.
See also: com.atlassian.maven.plugin.clover.internal.AbstractCloverMojo.licenseLocation

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. If not provided, Clover will use a bundled license key.
See also: com.atlassian.maven.plugin.clover.internal.AbstractCloverMojo.license

Specifies the custom method contexts to use for filtering specific methods from Clover reports.

e.g.

<main>public static void main\(String args\[\]\).*</main>

will define the context called 'main' which will match all public static void main methods.

Specifies the custom method contexts to use for filtering specific methods from Clover reports. This is more detailed format compared to methodContexts, which allows to set also code metrics to be matched. Example:

<methodWithMetricsContexts>
    <methodWithMetricsContext>
        <name>simpleGetter</name> <!-- (mandatory) -->
        <regexp>public .* get.*\(\)</regexp> <!-- (mandatory) -->
        <maxComplexity>1</maxComplexity> <!-- at most 1 cycle (optional) -->
        <maxStatements>1</maxStatements> <!-- at most 1 statement (optional) -->
        <maxAggregatedComplexity>2</maxAggregatedComplexity> <!-- no more than 2 cycles including inline classes (optional) -->
        <maxAggregatedStatements>10</maxAggregatedStatements> <!-- no more than 10 statements including inline classes (optional) -->
    </methodWithMetricsContext>
    <!-- can add more methodWithMetricsContext -->
</methodWithMetricsContexts>

will define a context called 'simpleGetter' which matches all public getXyz() methods containing at most one statement; this statement may contain more complex logic (an anonymous inline class) but not bigger than 9 statements.

List of all artifacts for this Clover plugin provided by Maven. This is used internally to get a handle on the Clover JAR artifact.

Note: This is passed by Maven and must not be configured by the user.

The Maven project instance for the executing project.

Note: This is passed by Maven and must not be configured by the user.

If set to 'false', test results will not be recorded; instead, results can be added via the <testResults> fileset at report time. Useful when a test uses a custom Rule expecting an exception, which OpenClover cannot recognize.

Remote repositories used for the project.

Try to protect your build from installing instrumented artifacts into local ~/.m2 cache or deploying them to a binaries repository. If this option is enabled, Clover will fail a build whenever it detects that 'install' or 'deploy' phase is about to be called. It will also fail a build if it detects that an artifact having multiple classifiers (e.g. "-clover-tests.jar"), which are not supported by Maven, is about to be installed under original name (e.g. "-tests.jar").

Please note that this flag may not protect from all possible cases.

When creating the clover.jar dependency, what scope to use. This may be one of: compile, test, provided etc. If not specified - provided will be used.

If set to true, Clover will add several properties to the build configuration which disable a build failure for following plugins:

• maven-surefire-plugin (maven.test.failure.ignore=true)
• maven-failsafe-plugin (maven.test.failure.ignore=true)
• maven-checkstyle-plugin (checkstyle.failOnViolation=false)
• maven-pmd-plugin (pmd.failOnViolation=false)

Thanks to this, build continues despite test failures or code validation failures and thus it is possible to generate a Clover coverage report for failed tests at the end of the build.

Note: before version 3.1.9 the testFailureIgnore property was set to true for the forked Clover lifecycle ('instrument' goal) for 'test' and 'integration-test' phases. Since 3.1.9 it is no longer set.

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.

A flag to indicate not to run clover for this execution. If set to true, Clover will not be run.

By default, Clover Maven Plugin generates the ${java.io.tmpdir}/grover*.jar file during setup, which is next being added as the dependent artifact to the build. As the file has generated, unique name and the jar is not being removed at the end of the build, these files can litter the temporary directory.

In case when there is no Groovy code in the project, this parameter can be set to true in order to disable generation of grover.jar artifact.

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.

Sets the granularity in milliseconds of the last modification date for testing whether a source needs reinstrumentation.

Specifies the custom statement contexts to use for filtering specific statements from Clover reports. e.g.

<log>^LOG\..*</log>

defines a statement context called "log" which matches all LOG statements.

Specifies a custom test detector configuration. Useful in case your tests are not following JUnit/TestNG naming convention. Example:

<testSources>
   <includes>
       <include>**/*</include>
       <include>*WebTest.java</include>
       <include>**/*IT.java</include>
   </includes>
   <excludes>
       <exclude>deprecated/**</exclude>
   </excludes>
   <testClasses>
       <testClass> <!-- 0..N occurrences -->
           <name>.*Test</name>
           <super>WebTest</super>
           <annotation>@Repeat</annotation>
           <package>org\.openclover\..*</package>
           <tag>@chrome</tag>
           <testMethods> <!-- 0..N occurrences -->
              <testMethod>
                  <name>check.*</name>
                  <annotation>@Test</annotation>
                  <tag>@web</tag>
                  <returnType>void</returnType>
              </testMethod>
           </testMethods>
       </testClass>
   </testClasses>
</testSources>

Note: every tag is optional.

Whether or not to include the -clover classifier on artifacts.

Use the fully qualified package name for java.lang.* classes.

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.