Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
NameJava Ecosystem
Latest version2.1.3 ( 25 June 2013 march 2014 )
Requires SonarQube version34.62 or higher ( check version compatibility )
LicenseGNU LGPL 3
Issue tracker
titleLive example

If you want to see a live example of the capabilities of the Java Ecosystem, you can have a look at SonarQube on SonarQube.

Description / Features

The Java Ecosystem is a set of plugins used to monitor the quality of Java projects within SonarQube.

It is compatible with the SonarQube Eclipse plugin to track issues while coding. It is also compatible with the Issues Report plugin to run pre-commit local analysis.


The Java Ecosystem is a set of plugins:


On top of the coding rules provided by the SonarQube engine


Note that by , you can activate rules from CheckstyleFindBugsPMDClirr, and fb-contrib. However, we highly recommend that you limit your Quality Profiles to from the SonarQube engine because we believe they are faster, more accurate (fewer false positives and false negatives), and more usable (they have better descriptions, etc). Read this blog post for more details.


By default the Java Ecosystem is provided with SonarQube. You  You can update it from the Update Center (since SonarQube 3.5) or  or download the latest release from this page header. Once the Java Ecosystem is installed, other plugins are available for download: Emma, Clover, etcDon't forget to check the upgrade notes.


Run a SonarQube Analysis


Sample projects for each analyzer are available on GitHub that can be browsed or downloaded: /projects/languages/java


  • The source directory should must be set to the directory containing the top parent package. For  For example, if your directory structure is 'src/main/java/com/mycompany/...', the source directory must be set to 'src/main/java'.
  • The source directory tree has to must match the package declaration. For  For example, the following class:
Code Block
package com.mycompany.mypackage;

must be located in the following directory: [mySourceDirectory]/com/mycompany/mypackage/ Otherwise  Otherwise you would get such an error like below while running your analysis:

Code Block
Exception in thread "main" org.sonar.batch.bootstrapper.BootstrapException: org.sonar.squid.api.AnalysisException: Got an exception - org.sonar.squid.api.AnalysisException: The source directory does not correspond to the package declaration com.mycompany.mypackage, file : ..\src\


The default code coverage engine for unit tests can be set in Settings > Configuration > General Settings > Java > Code coverage plugin property.

By default the code coverage engine is JaCoCo, but CoberturaEmma or Clover can also be used.


To deal with integration tests and code coverage, see Code Coverage by Integration Tests for Java Project tutorial.

Advanced Settings

Documentation on advanced parameters is available on the Analysis Parameters page.

Advanced parameters specific to Java are:

KeyDescriptionDefault value

Compatibility of your source code regarding Java version.

This property is not used by the SonarQube core but can be used by Java SonarQube plugins like the PMD plugin. 



See Java Ecosystem FAQ.


See Metrics documentation page.



To Go Further


New coding rules can be added using XPath. See the related documentation.


Change Log

JIRA Issues
titleVersion 1.3


JIRA Issues
titleVersion 1.2



Upgrade Notes

Version 2.0

This version no longer includes the Checkstyle and PMD plugins. Therefore, you should install those two plugins if you're still using some of their rules.

All the valuable rules from PMD and Checkstyle were rewritten based on our own SSLR technology. These rules are now available in the SonarQube repository. Deprecated rules from PMD and Checkstyle are flagged as so and their replacement is stated in the rule description:

Image Added

See for more details.

Version 1.5

  • Property sonar.surefire.reportsPath has been removed and replaced by sonar.junit.reportsPath.