Sonar 2.8 in screenshots
The Sonar team is proud to announce the release of Sonar 2.8. As usual, this new release includes improvements, bug-fixes and also new features that we believe are worth stopping your daily work for a couple of minutes to check out.
The main functionality is the support of manual code reviews. Coming back to the wikipedia definition of code review...
Code review is systematic examination of computer source code. It is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers' skills. Reviews are done in various forms such as pair programming, informal walkthroughs, and formal inspections.
... there are clearly two sides : automated and manual. Until version 2.8, Sonar only supported automated code reviews.
Manual code review
A human dimension has been added to automatic inspection with three new features :
- Discussions about violations
- Assignment of violations
- Flag violations as false-positives. They will be ignored during next analysis.
Sometimes violations do not relate to a specific package or file but to the entire project. It's for example the case with the Clirr plugin when a class should not have been removed. Such violations are now fully integrated to the violations drilldown page :
Compare Quality profiles
A new service provides the capability to compare two Quality Profiles. It highlights differences between rules configurations : rules only activated in one profile and rules activated with different settings.
Thanks to Julien Henry (Serli) for this great contribution.
So, what is going to keep us busy next ? We believe that manual code reviews add a new dimension to Sonar and this dimension must be integrated as much and simply as possible to the development process and especially to sonar-eclipse.
This is time to now let you give a try to the new version. The release notes of Sonar 2.8 are available in the download page. Reading the installation or upgrade guides is much recommended.