The Maven 2 and 3 Clover plugin produces Clover reports from Maven 2 and 3 projects.
On this page:
How to quickly set up basic Clover configuration in settings.xml and pom.xml and run Clover's goals from a command line.
How to set which source files shall be instrumented, control level of instrumentation, set JDK level and location of coverage data.
How to choose report formats, generate historical reports and customize report content.
How to set a coverage level as a quality gate and fail a build if it drops below certain threshold or drops compared to a previous build.
Working with distributed systems
- Using Distributed Per-test Coverage
- Using Clover in various environment configurations
- Using Clover for web applications
Working with multi-module projects
You can use the clover2:aggregate goal to combine the Clover databases of child projects into a single database at the parent project level.
Because of this Maven bug, aggregation of databases occurs before the child databases have been generated, when you use the
You can create Clover reports for a multi-module project with the command line
mvn clover2:setup test clover2:aggregate clover2:clover.
Using Clover with other Maven plug-ins
- Compiling Groovy with GMaven plugin
- Compiling Groovy with Groovy Eclipse Plugin
- Using Clover via the maven-antrun-plugin
- Using with Surefire and Failsafe Plugins
- Using Clover with the GWT-maven plugin
- Using Clover with JAXB plugin
- Using Clover with the maven-bundle-plugin
- Using Clover with Maven Tycho Plugin