This analyzer is recommended to launch analysis on Maven projects.
Analyze a Maven Project
Analyzing a maven project consists of running a maven goal in the directory where the pom.xml sits. If possible, an install goal should be performed prior to the sonar one.
skipTests=true not to run unit tests twice: during the install goal and again during the sonar goal. You can also deactivate the integration tests execution. Please refer to the Maven documentation.
When the above configuration is not possible, you can run an analysis in one command, but unit tests will run twice: once in the install goal and once in Sonar. Do not use the DskipTests=true parameter, otherwise Sonar will not execute unit tests and therefore not report on them.
The -Dmaven.test.failure.ignore=true is there to make sure that event if unit tests fail, the analysis will happen
For advanced features such as reusing existing unit test reports, you can define advanced parameters. These parameters can be defined:
in the Maven command-line (see next section):
in the properties section of pom.xml:
Note that command-line properties override pom properties.
How to fix version of Maven plugin
It is recommended to lock down versions of Maven plugins. Two versions of the Sonar maven plugin exist, one for Maven 2 and one for Maven 3. Fixing its version depends on the Maven versions used to analyse the project :
Project analyzed with Maven 2 only
Add the following code to pom.xml :
Project analyzed with Maven 3 only
Project analyzed with both Maven 2 and Maven 3
Reuse existing unit test reports
If you generates JUnit and Cobertura/Clover/Emma reports with your build mechanism you can configure Sonar in order to collect them. To do that, you must add the following lines in your pom.xml file:
The property sonar.cobertura.reportPath can be replaced by sonar.clover.reportPath if you use Clover instead of Cobertura.