Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: SQALE limitation

**Contributions are welcome. Join the effort !**

Extension plugin for Android Lint in SonarQubeTM.

The idea is to visualize Android Lint errors directly in SonarQubeTM, in the same way as findbugs / PMD / checkstyle errors are reported.

You can give a try:
- clone the repo,
- mvn clean install,
- copy the jar in your SONAR_HOME/extensions/plugins folder,
- restart SonarQubeTM
- use the lint mojo of the android-maven-plugin (
- mvn sonar:sonar -Dsonar.profile="Android Lint" in your project
- That's it !

This project is part of a larger effort to industrialize Android development, you can have a look at this other project (

Wiki Markup
Your browser does not support iframes.

Description / Features

This plugin enhances the Java Plugin to analyze Android projects within SonarQube:

  • Adds a new set of rules based on Android lint
  • On top of Java files, Android Manifest and resources (such as layouts or pictures) are analyzed

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 Android SDK must be installed on the machine(s) running the SonarQube analyses. The ANDROID_HOME environment variable should be configured to point to the installation directory of the Android SDK.

Note that you have to install the different Patforms/API that your projects are built with.

Include Page
Include - Plugin Installation
Include - Plugin Installation


Run an Analysis with the SonarQube Runner (Recommended method)

To run an analysis of your Android project, use the SonarQube Runner.

A sample project is available on GitHub that can be browsed or downloaded/projects/languages/android/android-sonarqube-runner

Run an Analysis with the other Analyzers

Maven and Ant can also be used to launch analysis on Android projects.

Code Coverage

To display code coverage data:

  1. Prior to the SonarQube analysis, execute your unit tests and generate the Emma 2.0 reports (.em and .ec files)
  2. Import these reports while running the SonarQube analysis by setting the property to the path of the directory containing the Emma reports. The path may be absolute or relative to the project base directory for standard projects, relative to the module base directory for multi-module projects.


See Metrics documentation page.

Extending Coding Rules using XPath

See Extending Coding Rules for Java.


Currently, it is not possible to use SQALE with Android projects. This feature will be available in the next Android plugin version.
See the corresponding issue.