This documentation is for Clover 3.3.x. Earlier versions are available here.

Skip to end of metadata
Go to start of metadata

This page lists the various ways in which you can specify your Clover for Maven 2 license. You can try one of the following processes if your Clover license is not being recognised correctly.

(warning) 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.

Specifying your license location in the pom.xml file

You can set this property to point to your clover license in the pom.xml file. In the example below, replace'/path/to/clover.license' with the path to your Clover license file:

Embedding your license in the pom.xml file

You can configure the Maven 2 plugin to include the license data in your pom.xml file. Simply add a <license> element inside <configuration> and make its contents contain the four line Atlassian license string.

(warning) Some Atlassian licenses may contain XML characters, so you will need to ensure you wrap your license in CDATA tags:

This will make the Maven build less reliant on local file system layout, or the availability of remote servers.

Specifying your license location in your ~/.m2/settings.xml file

You can set this property to point to your clover license in your settings.xml file. In the example below, replace'/path/to/clover.license' with the path to your Clover license file:

Specifying your license on the command line

To specify your license at the command line, specify a property as follows (replacing '/path/to/clover.license' with the path to your Clover license file):

  • No labels