Versions Compared


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


NameJava Ecosystem
Latest version2.3 ( 26 june 2014 )
Requires SonarQube version4.2 or higher ( check version compatibility )
LicenseGNU LGPL 3
Issue trackerhttp://




titleLive example

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

titleJava bytecode is required

Analysing a Java project without providing the Java bytecode of the source files and of all the project dependencies (jar files) is possible but will lead to highly decrease the number of issues found by the analyzer (false-negatives). Moreover the detection of cycles between packages and the display of the DSM will be automatically deactivated. As soon as a class required to efficiently do an analysis is missing a warning like the following one is logged :

[WARN] [08:40:21.769] Class 'XXXXXX' is not accessible through the ClassLoader.


Description / Features

The ecosystem enables analysis of Java projects within Sonar.


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

On top of the coding rules provided by the SonarQube engine, 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.

If your Quality Profile contains rules from the SonarQube engine or FindBugs rules, then byte code will be required by the analysis. This Java Ecosystem is able to analyse any kind of java source files whatever is the version of Java they comply to.


By default the Java Ecosystem is provided with Sonar.As any other plugins, you can update it through the SonarQube. You can update it from the Update Center or download new version into the SONAR_HOME/extensions/plugins directory. Then restart the Sonar serverthe latest release from this page header. Don't forget to check the upgrade notes.


Run a


SonarQube Analysis

To run an analysis of your JavaScript Java project, use the Sonar Runner.A sample project is you can use the following analyzers:

Note that you must provide both source code and compiled byte code if the Quality Profile in use contains either SonarQube-native rules, or FindBugs rules.

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

titleFor versions prior to 2.1
  • The source directory must be set to the directory containing the top parent package. For example, if your directory structure is src/


Run a Sonar Analysis with the other Analyzers


  • main/java/com/mycompany/..., the source directory must be set to src/main/java.
  • The source directory tree must match the package declaration. For example, the following class:

    Code Block
    package com.mycompany.mypackage;

    must be located in the following directory: [mySourceDirectory]/com/mycompany/mypackage/ Otherwise you would get 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\

Unit Tests and Code Coverage Reports


Extending Coding Rules using XPath

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

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

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

To Go Further


Change Log

JIRA Issues
titleRelease 1.1

Upgrade Notes

Version 2.2

It is no longer possible to let SonarQube drive the execution of the unit tests. You now have to generate the JUnit and code coverage (JaCoCo or Cobertura or Clover) reports prior to the SonarQube analysis and then feed SonarQube with those reports.

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.