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 11 Next >>
Live example

If you want to see a live example of the capabilities of the Java Ecosystem, you can have a look at Sonar on Sonar.

Description / Features

The Java Ecosystem is a set of Sonar plugins used to monitor the quality of Java projects within Sonar.

Installation

The Java Ecosystem is provided with Sonar.

As any other plugins, you can update it through the Update Center or download new version into the SONAR_HOME/extensions/plugins directory. Then restart the Sonar server.

Usage

Run a Sonar Analysis

To launch a Sonar analysis of your Java project, it is recommended to use:

Sample projects for each analyzer are available on GitHub that can be browsed or downloaded: /projects/languages/java

Tests and Code Coverage

The default code coverage engine for unit tests can be set in Settings > Configuration > General Settings > Java > Code coverage plugin property.

By default the code coverage engine is JaCoCo but Cobertura, Emma or Clover can also be used.

To see how to deal with unit tests and code coverage for Java project in Sonar, see Code Coverage by Unit Tests for Java Project tutorial.

To see how to deal with integration tests and code coverage for Java project in Sonar, see Code Coverage by Integration Tests for Java Project tutorial.

Advanced Parameters

Documentation on advanced parameters is available on the Analysis Parameters page.

Advanced parameters specific to Java are:

KeyDescriptionDefault value

sonar.skipDesign

Deactivate Java bytecode analysis. The Java bytecode is analyzed by Sonar in order to extract dependencies between packages and files. These dependencies are used for instance to display the DSM (Dependency System Matrix). This bytecode analysis can be deactivated.

false

sonar.java.source

Java version of the source code. This property is not used by the Sonar core but can be used by Java Sonar plugin like the PMD plugin. 

1.7 since Sonar 2.12

Android

TODO

Extending Coding Rules using XPath

New coding rules can be added using XPath. See the related documentation.

To navigate the AST, download the SSLR Java Toolkit.

Change Log

Release 1.1 (15 issues)
Type Key Summary Priority
Improvement SONARJAVA-18 Grab violations directly from findbugs without xml-report generation Major
Bug SONARJAVA-80 L10n files are not in the correct folder Major
Improvement SONARJAVA-20 Upgrade to SSLR 1.16 and switch to lexerless parser Major
Improvement SONARJAVA-3 The literal "42L" should be lexed as a LONG_LITERAL instead of a INTEGER_LITERAL Major
Improvement SONARJAVA-2 The literal "42.0" should be lexed as a DOUBLE_LITERAL instead of a FLOATING_LITERAL Major
Bug SONARJAVA-1 OutOfMemoryError when attempting to lex an unterminated single quote Major
Bug SONARJAVA-14 findbugs-result.xml contains invalid character entity Major
Improvement SONARJAVA-15 When using the property 'sonar.findbugs.excludesFilters' an INFO log should be generated to clearly show that the external Findbugs filter is taken into account Major
Improvement SONARJAVA-39 New property 'sonar.java.coveragePlugin' Major
Improvement SONARJAVA-4 Upgrade to Checkstyle 5.6 Major
New Feature SONARJAVA-5 Rule: Generic Java rule to define some homemade checks with an XPath expression Major
Improvement SONARJAVA-17 When the last line of a source code file is a blank line, this line is not counted in the "lines" measure Major
Bug SONARJAVA-44 The IT and Overall code coverage should not be computed when the code coverage by unit tests is not computed with jacoco Minor
Improvement SONARJAVA-22 The two properties of the Checkstyle rule 'RegexpHeaderCheck' should be TEXT Trivial
Bug SONARJAVA-84 Typo in the Checkstyle rule "ReturnCount" Trivial

Labels
  • None