Plugin documentation

Goals available for this plugin:

Goal Report? Description
clover2:log No Provides information on the current Clover database.
clover2:instrumentInternal No Instrument source roots.

Note 1: Do not call this MOJO directly. It is meant to be called in a custom forked lifecycle by the other Clover plugin MOJOs.

Note 2: We bind this mojo to the "validate" phase so that it executes prior to any other mojos

clover2:save-history No Save a Clover history point.
clover2:instrument No Instrument all sources using Clover and forks a custom lifecycle to execute project's tests on the instrumented code so that a Clover database is created.

Note: We're forking a lifecycle because we don't want the Clover instrumentation to affect the main lifecycle build. This will prevent instrumented sources to be put in production by error. Thus running mvn install on a project where this instrument goal has been specified will run the build twice: once for building the project as usual and another time for instrumenting the sources with Clover and generating the Clover database.

clover2:check No Verify Test Percentage Coverage (TPC) from an existing Clover database and fail the build if it is below the defined threshold. The check is done on main Clover databases and also on merged Clover databases when they exist.
clover2:aggregate No 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...
clover2:clover Yes Generate a Clover report from existing Clover databases. The generated report is an external report generated by Clover itself. If the project generating the report is a top level project and if the aggregate configuration element is set to true then an aggregated report will also be created.

Note: This report mojo should be an @aggregator and the clover:aggregate mojo shouldn't exist. This is a limitation of the site plugin which doesn't support @aggregator reports...

System Requirements

The following specifies the minimum requirements to run this Maven plugin:

Maven 2.0
JDK 1.1
Memory No minimum requirement.
Disk Space No minimum requirement.

Usage

You could run 'mvn -up' to get the latest version of this plugin, or specify the version in your project's plugin configuration:

<project>
  ...
  <build>
    <!-- To define the plugin version in your parent POM -->
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>com.atlassian.maven.plugins<groupId>
          <artifactId>maven-clover2-plugin<artifactId>
          <version>2.3.1<version>
        </plugin>
        ...
      </plugins>
    </pluginManagement>
    <!-- To use the plugin goals in your POM or parent POM -->
    <plugins>
      <plugin>
        <groupId>com.atlassian.maven.plugins<groupId>
        <artifactId>maven-clover2-plugin<artifactId>
        <version>2.3.1<version>
      </plugin>
      ...
    </plugins>
  </build>
  ...
  <!-- To use the report goals in your POM or parent POM -->
  <reporting>
    <plugins>
      <plugin>
        <groupId>com.atlassian.maven.plugins<groupId>
        <artifactId>maven-clover2-plugin<artifactId>
        <version>2.3.1<version>
      </plugin>
      ...
    </plugins>
  </reporting>
  ...
</project>
For more information, see "Guide to Configuring Plug-ins"