Message-ID: <192089515.10891.1416750489928.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10890_1111510224.1416750489927" ------=_Part_10890_1111510224.1416750489927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Java plugin is used to monitor the quality of Java within SonarQube.=
With additional plugins= , you can activate rules from Checkstyle, Fi= ndBugs, PMD, Clirr, and fb-contrib. However, we highly recommend that y= ou limit your Quality Profiles<= /a> to from the SonarQube engine because we believe they are faster, m= ore accurate (fewer false positives and false negatives), and more usable (= they have better descriptions, etc). Read this blog post for more deta= ils.
If your Quality Profile contains rules from the SonarQube engine or Find= Bugs rules, then byte code will be required by the analysis. This Java= Ecosystem is able to analyse any kind of java source files whatever is the= version of Java they comply to.
By default the Java plugin is provided with SonarQube. You can upda= te it from the Update Center&n= bsp;or download the latest release from this page header. Don't forget to c= heck the upgrade notes.
To run an analysis of your Java project, you can use the following analyzers:
Note that you must provide both source code and compiled byte code if th= e Quality Profile in use contains either SonarQube-native rules, or FindBug= s rules.
To provide compiled bytecode and dependencies to the analysis, prior to =
version 2.5 please refer to the Analysis Parameters Page and use
From version 2.5, if you are not using maven, use the two following prop= erties :
|sonar.java.binaries||Comma-separated paths to directori= es containing the compiled bytecode files corresponding to your s= ource files|
Comma-separated paths to files with third-par=
ty libraries (JAR or Zip files).
sona= r.java.libraries=3Dpath/to/specific/library/myLibrary.jar,path/to/library/*= .jar,directory/**/*.jar
To deal with unit tests and code coverage, see Code Coverage by Unit T= ests for Java Project tutorial.
To deal with integration tests and code coverage, see Code Cove= rage by Integration Tests for Java Project tutorial.
It is no longer possible to let SonarQube drive the execution of the uni= t tests. You now have to generate the JUnit and code coverage (JaCoCo or Cobertura or = Clover) reports prior to the SonarQube analysis and then feed SonarQube= with those reports.
All the valuable rules from PMD and Checkstyle were rewritten based on o= ur own SSLR technology. These rule= s are now available in the SonarQube repository. Deprecated rules from PMD = and Checkstyle are flagged as so and their replacement is stated in the rul= e description:
sonar.surefire.reportsPathhas been removed = and replaced by