Clover-for-Maven 2 Quick Start Guide

To get started with Clover-for-Maven 2, carry out the following steps.

Install Clover-for-Maven 2 by adding it to your Maven 2 build file (pom.xml):

Set up your pom.xml by adding:
pom.xml
```
<build>
    <plugins>
        ...
        <plugin>
            <groupId>com.atlassian.maven.plugins</groupId>
            <artifactId>maven-clover2-plugin</artifactId>
            <version>${clover.version}</version>
        </plugin>
        ...
    </plugins>
</build>
```
Either change ${clover.version} to the current Clover version, or define a property in your pom.xml that sets this value.

Clover ships with a 30 day evaluation license. After 30 days you need a valid Clover license file to run Clover. You can obtain a free 30 day evaluation license or purchase a commercial license at http://my.atlassian.com. You will need to set up your licence, as a <licenseLocation> element in your pom.xml configuration file.
Now, simply invoke Clover with Maven on the command line. This will instrument your sources, build your project, run your tests and create a Clover coverage database.

You can also have Clover run as part of your build. Learn how.

There are three basic parts executed when recording code coverage with Clover.

The command clover2:aggregate goal is used for merging coverage data generated by multi-module projects.

Hence, if you use the following code:

mvn clover2:setup test clover2:aggregate clover2:clover

This will create a coverage report, which will be created in this directory:

target/site/clover

Clover should now be fully set up for basic operation.

For more license configuration options, see the FAQ pages.

For more general instructions, see the Clover-for-Maven 2 User's Guide.

Once you have Clover fully integrated with your build, you can move on to Using Test Optimization with Clover-for-Maven 2.