Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Unknown macro: {iframe}

Your browser does not support iframes.

Description / Features

The Issues Report plugin provides the ability to run local Sonar analyses. The main use case is for a developer to check his/her code before pushing it to the SCM.

It generates an HTML report that displays a list of violations that can be filtered by severity, new violations only, etc.

It supports all languages.

Here's an example of HTML report that you can download:

Sonar Eclipse Plugin

Note that to perform local analyses, a Sonar Eclipse plugin is also available. It currently supports Java, C/C++ and Python.


  1. Install the Issues Report plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server


Note that you do not need to install any local Sonar server and database.

Just run a Sonar analysis on your project with your favorite analyzer (Sonar RunnerMaven or Ant). To run the analysis locally (without making the results available on the remote Sonar server), just set the 'sonar.dryRun' property to 'true' and make sure that the '' is properly set to match your remote Sonar server.

To get a local report:

  • To generate an HTML report, set the property 'sonar.issuesReport.html.enable' to 'true'
  • To set the location of the HTML report, set the property 'sonar.issuesReport.html.location': absolute path or relative path to the working directory; default is '.sonar/issues-report.html' for the Sonar Runner and Ant, 'target/sonar/issues-report.html ' for Maven.
  • To display a short report in the console, set the 'sonar.issuesReport.console.enable' to 'true':

A useful feature is to limit the scope of the analysis to the files that have been created or modified. To do so, the 'sonar.inclusions' property can be set.

In the following example, Sonar will only check the 'myProgram.cbl' Cobol program and ignore the other programs of the application. The analysis will be local: nothing will be pushed to the database, thus the results will not be available through the Sonar server web interface. An HTML report will be generated to display the list of violations on the 'myCobolProgram.cbl' file:


sonar-runner -Dsonar.dryRun=true -Dsonar.issuesReport.html.enable=true -Dsonar.inclusions=src/myCobolProgram.cbl

Multi-module project compatibility

Note that the Issues Report plugin is not yet compatible with multi-module projects. See


Change Log

type key summary priority

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

  • No labels