Skip to content
No description, website, or topics provided.
Java FreeMarker CSS
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
src SONARISSRP-5 Use RuleFinder to get rule name Aug 28, 2014
.gitignore Initial creation of Issues Report plugin. Feb 19, 2013 Create file Aug 10, 2015
.travis.yml Create .travis.yml May 21, 2015 Move documentation to README May 30, 2016
pom.xml Update scm and issue urls in pom May 30, 2016

Issues Report Plugin

Build Status

Description / Features

The Issues Report plugin provides the ability to generate HTML report on issues. The main use case is for developers to check the code they have added or changed before pushing it back to the SCM.

Issues can then be filtered by severity, new issues only, etc.

SonarQube Eclipse Plugin

Note that while the Issues Report plugin supports every language, there is also support for certain languages within the IDE. See SonarLint for Eclipse, IntelliJ, and VisualStudio.


As the main use case is for developers to check the code they have added or changed before pushing it back to the SCM, the Issues Report plugin is usually used in preview mode. This is this usage that is detailed below.

Install your favorite scanner (SonarQube Scanner, SonarQube Scanner for Maven or SonarQube Scanner for Ant) on your local machine. You only have to set the "" property to point to your remote SonarQube server (connection settings to the remote database do not have to be provided for a preview analysis as no data is pushed to the database). Note that you don't need to install any SonarQube server on your local machine.

Copy the configuration file ('', 'pom.xml', etc.) that is used to analyze the project on the remote server to your local machine. Make sure that the "sonar.sources" property refers to the directory containing the source code on your local machine (or update it accordingly). The tree structure of the source code on your local machine must match the tree structure that has been remotely analyzed by SonarQube.

To get an HTML report, set the "sonar.issuesReport.html.enable" property to true. To define its location, set the "sonar.issuesReport.html.location" property to an absolute or relative path to the destination folder for the HTML report. The default value is '.sonar/issues-report/' for the SonarQube Runner and Ant, and 'target/sonar/issues-report/' for Maven. By default 2 html reports are generated:

  • The full report (default name is issues-report.html)
  • The light report (default name is issues-report-light.html) that will only contains new issues.

The light report is useful when working on legacy projects with a lot of many issues, since the full report may be hard to display in your web browser. You can skip full report generation using property "sonar.issuesReport.lightModeOnly".

You can also configure the filename of the generated html reports using property "".

To display a short report in the console, set the "sonar.issuesReport.console.enable" property to true:

Finally, run a preview analysis that generates an HTML report:

# Since SonarQube 4.0
sonar-runner -Dsonar.analysis.mode=preview -Dsonar.issuesReport.html.enable=true

# Prior to SonarQube 4.0
sonar-runner -Dsonar.dryRun=true -Dsonar.issuesReport.html.enable=true

Even more useful, you can limit the scope of the analysis to the files that have been recently created or modified (i.e. incremental mode):

# Since SonarQube 4.0
sonar-runner -Dsonar.analysis.mode=incremental -Dsonar.issuesReport.html.enable=true
# Prior to SonarQube 4.0, the files have to be manually listed
sonar-runner -Dsonar.dryRun=true -Dsonar.issuesReport.html.enable=true -Dsonar.inclusions=myCobolProgram.cbl,...
You can’t perform that action at this time.