Description / Features
Get code coverage with Atlassian Clover.
In order to make Sonar use the Clover Java code coverage engine, the property 'sonar.java.coveragePlugin' must be set to 'clover'. It can be set in different locations:
- Global settings (Settings > Configuration > General Settings > Java). It will apply to all Java projects.
- Project settings (Project > Configuration > Settings > Java). It will apply to this specific project.
- Build tool settings, for example a Maven property in the pom or a command-line property.
From the settings pages, the version of the Maven Clover plugin to be used and the license key can be set.
By uploading the license key (clover 1 or clover 2) into Sonar, you will benefit from a centralized configuration.
By default, the sonar-plugin-clover1 runs the maven-clover-plugin.
By default, the sonar-plugin-clover2 runs the maven-clover2-plugin.
In case the Clover plugin is defined in the pom.xml of your project, Sonar will use the version defined in the pom with its attached configuration.
See the Code Coverage by Unit Tests tutorial.
- Problems with GWT - see SONARPLUGINS-1048
|Release 2.9 (2 issues)|
|SONARPLUGINS-2397||Support the new property 'sonar.java.coveragePlugin'|
|SONARPLUGINS-2363||Upgrade to Sonar 3.0 API|
|Release 2.8 (1 issues)|
|SONARPLUGINS-1147||Clover should support Maven 3 by default|
|Release 2.7 (1 issues)|
|SONARPLUGINS-1031||Support coverage of new code|