|Latest version||1.2 ( 13 March 2013 )|
|Requires Sonar version||3.4 or higher ( check version compatibility )|
|License||GNU LGPL 3|
If you want to see a live example of the capabilities of the Java Ecosystem, you can have a look at Sonar on Sonar.
The Java Ecosystem is a set of Sonar plugins used to monitor the quality of Java projects within Sonar.
It is compatible with the Sonar Eclipse plugin to track violations while coding. It is also compatible with the Issues Report plugin to run pre-commit local analysis.
The Java Ecosystem is a set of plugins:
Note that by default the Java Ecosystem is provided with Sonar.
You can update it from the Update Center (since Sonar 3.5) or download the latest release from this page header.
To launch a Sonar analysis of your Java project, it is recommended to use the following analyzers:
Sample projects for each analyzer are available on GitHub that can be browsed or downloaded: /projects/languages/java
package com.mycompany.mypackage; ...
must be located in the following directory: [mySourceDirectory]/com/mycompany/mypackage/MyClass.java. Otherwise you would get such an error while running your analysis:
Exception in thread "main" org.sonar.batch.bootstrapper.BootstrapException: org.sonar.squid.api.AnalysisException: Got an exception - org.sonar.squid.api.AnalysisException: The source directory does not correspond to the package declaration com.mycompany.mypackage, file : ..\src\MyClass.java ...
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 deal with unit tests and code coverage for Java project in Sonar, see Code Coverage by Unit Tests for Java Project tutorial.
To deal with integration tests and code coverage for Java project in Sonar, see Code Coverage by Integration Tests for Java Project tutorial.
Documentation on advanced parameters is available on the Analysis Parameters page.
Advanced parameters specific to Java are:
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.
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.
See Java Ecosystem FAQ.
See Metrics documentation page.
A sample project with code coverage computed with Emma is available on GitHub that can be browsed or downloaded: /projects/android
New coding rules can be added using XPath. See the related documentation.
To navigate the AST, download the SSLR Java Toolkit.