Description / Features

The Issues Report plugin provides the ability to run local Sonar analyses. The main use case is for a developer to check its 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 support all languages.

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

Installation

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

Usage

Run a Sonar analysis on your project with your usual analyzer (Sonar Runner, Maven or Ant).

To run the analysis without pushing the results to the database, set the 'sonar.dryRun' to 'true'. Then, the analysis will be run locally.

To get a local report:

• To generate an HTML report, set the property 'sonar.issuesReport.html.enable' to 'true'
• To set the localtion of this report, set the property 'sonar.issuesReport.html.location' (default is .sonar/issues-report.html)
• To display a short report on the console, set the 'sonar.issuesReport.console.enable' to 'true'

• Utilisation de la nouvelle propriété Sonar -Dsonar.inclusions=**/monFichier.toto pour limiter les fichiers à analyser

• Support du tracking des violations

To generate

Change Log

Release 1.2 (33 issues)
Type	Key	Summary	Priority
	SONARPLUGINS-2545	Rule: Avoid redeclaration of functions
	SONARPLUGINS-2546	Rule: Avoid usage of the same name for the declarations of both a function and a variable
	SONARPLUGINS-2538	Rule: Use Javascript strict mode with caution
	SONARPLUGINS-2536	Rule: Avoid trailing whitespaces
	SONARPLUGINS-2537	Rule: Newline at the end of file
	SONARPLUGINS-2533	Rule: Avoid redeclaration of variables
	SONARPLUGINS-2532	Rule: "eval" and "arguments" must not be bound or assigned
	SONARPLUGINS-2530	Rule: Do not use octal numbers
	SONARPLUGINS-2527	Rule: Function argument names should be unique
	SONARPLUGINS-2526	Rule: Duplicate property names not allowed in object literals
	SONARPLUGINS-2529	Rule: Do not use additional "future reserved words" as identifiers
	SONARPLUGINS-2519	Parser: Regular expression can contain empty class
	SONARPLUGINS-2518	Parser: Incorrect definition of grammar rule identifier
	SONARPLUGINS-2517	Parser: "future reserved words" can be used as identifiers in non-strict code
	SONARPLUGINS-2516	Parser: incorrect definition of grammar rule identifierName
	SONARPLUGINS-2515	Update the SQALE mapping for new rules
	SONARPLUGINS-2514	Rule: Do not use Internet Explorer's conditional comments
	SONARPLUGINS-2513	Misleading position of violation for rule AlwaysUseCurlyBraces
	SONARPLUGINS-2511	Empty violation message in LabelPlacementCheck
	SONARPLUGINS-2512	Rule: Avoid trailing comment
	SONARPLUGINS-2506	Rule: Avoid use of constructor functions for side-effects
	SONARPLUGINS-2503	Rule: Collapsible If statements
	SONARPLUGINS-2502	Rule: Avoid use of tabulation character
	SONARPLUGINS-2500	Rule: Avoid empty block
	SONARPLUGINS-2498	Rule: If ... else if constructs shall be terminated with an else clause
	SONARPLUGINS-2497	Rule: Avoid function with too many parameters
	SONARPLUGINS-2551	Incorrect computation of metrics in case of anonymous functions on same line
	SONARPLUGINS-2289	Parsing javascript running under linux
	SONARPLUGINS-2352	Use lexerless parser
	SONARPLUGINS-2524	The Coverage/Unit Tests widget should not be displayed by default on Javascript projects
	SONARPLUGINS-2520	Update properties descriptions
	SONARPLUGINS-2464	An unconditional break statement shall terminate every non-empty case-clause except latest
	SONARPLUGINS-2307	Incorrect complexity computation