|Table of Contents|
This analyzer is recommended to launch analysis on Java Maven project.
Analyzing a Maven Project
Analyzing a Maven project consists of running a Maven goal in the directory where the pom.xml file 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.
Make sure you're not using the eclipse plugin maven embedder. Define a new maven runtime pointing to your local maven install, use the latest maven eclipse plugin and uncheck "resolve workspace artifacts" in the maven project launch window.
|Advanced Reactor Options|
Note that Advanced Reactor Options (such as "--projects" and "--resume-from") are not supported by Sonar and should not be used.
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 the sonar one. 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 even if unit tests fail, the Sonar analysis will be performed.
Configuring the Sonar Analysis
A pom.xml file sample is available here.
Additional analysis parameters are listed on the Analysis Parameters page.
See also some complete examples here.
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 the pom.xml file:
The version 1.0-beta-1 is not supported anymore.