Skip to content
☕️ SonarJava : Java static analyzer for SonarQube & SonarLint
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
external-reports Prepare for next development iteration (#2442) Feb 19, 2019
its QA: Remove deprecated resetData method (#2458) Mar 22, 2019
java-checks SONARJAVA-3048 Parse new java 12 switch expression (#2450) Mar 22, 2019
java-frontend SONARJAVA-3048 Parse new java 12 switch expression (#2450) Mar 22, 2019
sonar-jacoco-listeners Prepare for next development iteration (#2442) Feb 19, 2019
sonar-java-plugin Prepare for next development iteration (#2442) Feb 19, 2019
.gitignore Ignore DS_Store on OSX (#2306) Oct 31, 2018
.travis.yml Change links from mailing lists to community forum Jun 11, 2018
LICENSE.txt Add License and copyright files (#1143) Dec 19, 2016
NOTICE.txt Update Readme, pom metadatas and add contributing and pr template files Apr 11, 2016 Remove note about jacoco-previous from (#2312) Nov 2, 2018 Check license compliance on Travis (#2031) May 25, 2018
sonarpedia.json update travis utils to version 55 Mar 13, 2019

SonarJava Build Status Quality Gate Coverage

SonarJava is a code analyzer for Java projects. Information about the SonarJava features is available here.

Build status (all branches)

Build Status


Useful links

Have question or feedback?

To provide feedback (request a feature, report a bug etc.) use the SonarQube Community Forum. Please do not forget to specify the language (Java!), plugin version and SonarQube version.

If you have a question on how to use plugin (and the docs don't help you), we also encourage you to use the community forum.


Topic in SonarQube Community Forum

To request a new feature, please create a new thread in SonarQube Community Forum. Even if you plan to implement it yourself and submit it back to the community, please start a new thread first to be sure that we can use it.

Pull Request (PR)

To submit a contribution, create a pull request for this repository. Please make sure that you follow our code style and all tests are passing (Travis build is created for each PR).

Custom Rules

If you have an idea for a rule but you are not sure that everyone needs it you can implement a custom rule available only for you.


To run tests locally follow these instructions.

Build the Project and Run Unit Tests

To build the plugin and run its unit tests, execute this command from the project's root directory:

mvn clean install

Integration Tests

To run integration tests, you will need to create a properties file like the one shown below, and set the url pointing to its location in an environment variable named ORCHESTRATOR_CONFIG_URL.

# version of SonarQube Server


# Location of Maven local repository is not automatically guessed. It can also be set with the env variable MAVEN_LOCAL_REPOSITORY.

With for instance the ORCHESTRATOR_CONFIG_URL variable being set as:

export ORCHESTRATOR_CONFIG_URL=file:///home/user/workspace/

Before running the ITs, be sure your MAVEN_HOME environment variable is set.

Plugin Test

The "Plugin Test" is an integration test suite which verifies plugin features such as metric calculation, coverage etc. To launch it:

mvn clean install -Pit-plugin

Ruling Test

The "Ruling Test" are an integration test suite which launches the analysis of a large code base, saves the issues created by the plugin in report files, and then compares those results to the set of expected issues (stored as JSON files).

To run the test, first make sure the submodules are checked out:

git submodule init 
git submodule update

Launch ruling test:

cd its/ruling
mvn clean install -DskipTests=false

This test gives you the opportunity to examine the issues created by each rule and make sure they're what you expect. Any implemented rule is highly likely to raise issues on the multiple projects we use as ruling code base.

  • For newly implemented rule, it means that a first build will most probably fail, caused by differences between expected results (without any values for the new rule) and the new results. You can inspect these new issues by searching for files named after your rule (squid-SXXXX.json) in the following folder:

  • For existing rules which are modified, you may expect some differences between "actual" (from new analysis) and expected results. Review carefully the changes which are shown and update the expected resources accordingly.

All the json files contain a list of lines, indexed by file, expliciting where the issues raised by a specific rule are located. If/When everything looks good to you, you can copy the file with the actual issues located at:


Into the directory with the expected issues:


For example using the command:

cp its/ruling/target/actual/* its/ruling/src/test/resources/


Copyright 2012-2018 SonarSource.

Licensed under the GNU Lesser General Public License, Version 3.0

You can’t perform that action at this time.