This plugin allows you to capture code coverage reports from Clover. Jenkins will generate and track code coverage across time. This plugin can be used without the need to modify your build.xml.
We recommend reading the official Clover Documentation home page - you will find instructions how to integrate Clover with Ant, Maven, Grails and other tools.
In case of trouble, you may have a look at the Atlassian Answers page (questions tagged 'clover').
The maven-clover2-plugin is one of the plugins that highlights an issue with how Maven 2 handles aggregator goals.
Jenkins cannot handle maven aggregator goals with the maven2 project (alpha) project type due to how this project type calls Maven. In order to obtain multi-module clover reports, you must therefore use the free-style software project project type. In any case, the Jenkins Clover Plugin does not currently support the maven2 project (alpha) project type. In order to ensure that the correct aggregated report is generated, it is necessary to invoke maven multiple times.
The maven2 ear packaging will break if you use the clover goal at any time during the same invokation of maven if you ivoke the package or later phases (as it will see artifacts without a classifier and with the clover classifier, get confused and give up)
To work around this, you should configurer your root pom to include the <packaging>ear</packaging> targets only when you are not using clover... how to do this:
The above... hack... is why it is recommended to invoke maven three times. If you don't need this hack, you could simplify down to two invocations and specify the clover license file location in the pom.xml, i.e. install clover:instrument | -N clover:aggregate clove:site
Version 4.4.0 (July 18, 2014)
Version 4.3.0 (April 1, 2014)
Version 4.2.0 (October 23, 2013)
Version 4.1.0 (August 13, 2012)
Version 4.0.6 (May 13, 2012)
Version 4.0.5 (Jan 18, 2012)
Version 4.0.4 (Nov 8, 2011)
Version 4.0.2 (Jun 6, 2011)
Version 4.0.1 (May 7, 2011)
Skip to end of metadata Go to start of metadata