Message-ID: <846609626.2519.1406271845612.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2518_270801717.1406271845612" ------=_Part_2518_270801717.1406271845612 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
|Lates= t version||2.3= strong> ( 26 june 2014 )|
|Requi= res SonarQube version||4.2= strong> or higher ( check version compatibi= lity )|
|Licen= se||GNU LGPL 3|
|Sourc= es||https://github.com/SonarSour= ce/sonar-java|
The Java Ecosystem is a set of plugins used to monitor the quality of Ja= va within SonarQube.
On top of the coding rules provided by the SonarQube engine, you can act= ivate rules from Checksty= le, FindBugs, = PMD, Clirr, and fb-contrib. However, we highly recommend that you limit your Quality Profiles to from = the SonarQube engine because we believe they are faster, more accurate (few= er false positives and false negatives), and more usable (they have better = descriptions, etc). Read this blog post for more details.
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.
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 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