Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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:sonar one. Do not use the DskipTests=true parameter, otherwise Sonar will not execute unit tests and therefore not report on themthe unit tests will be executed at all.

Code Block
mvn clean install sonar:sonar -Dmaven.test.failure.ignore=true

The -Dmaven.test.failure.ignore=true is there to make sure that even if some unit tests fail, the Sonar SonarQubeTM analysis will be performed.

Configuring the


SonarQubeTM Analysis

A pom.xml file sample is available here.

Additional analysis parameters are listed on the Analysis Parameters page.


Since Sonar SonarQubeTM 3.4, if a project cannot be accessed anonymously, the 'sonar.login' and 'sonar.password' properties are required to run an analysis on this project. These properties have to be set to the credentials of a user having the 'User' role on this project. You can set them either:

  • directly on the command line by adding -Dsonar.login=myUser -Dsonar.password=myPassword
  • or in the pom.xml file
  • or in the Maven profile (settings.xml file)

A project cannot be anonymously accessed when either:

Sample Projects

To help you getting started, a simple project sample is available on github that can be browsed or downloaded: projects projects/languages/java/maven/java-maven-simple

How to Fix Version of Maven Plugin


Analyzing a Multi-module and Multi-language Project

Since Sonar SonarQubeTM 3.3, it is possible to run an analysis on a multi-module project whose modules contains source code from different languages.

To do so, just add the 'sonar.language' property to the pom of each module.

To help you getting get started, a multi-language project sample is available on github that can be browsed or downloaded: projects projects/languages/multi-language/multi-language-java-javascript-maven