Sonar 1.12 in screenshots
Here comes the 8th and last major Sonar release of the year. Like for all previous releases, this post is a summary of the new features through screenshots :
Read the rest of this page »
Here comes the 8th and last major Sonar release of the year. Like for all previous releases, this post is a summary of the new features through screenshots :
Read the rest of this page »
We’re happy to announce the release of Sonar 1.11. This new version contains more than 60 issues that have been resolved amongst which improvements, bug fixes, technical migrations and also several new features. Here are the most important ones in screenshots : Read the rest of this page »
We’re happy to announce the release of Sonar 1.10. This new version contains more than 40 improvements and bug fixes and also contains several new features. Here are the most important in screenshots :
Most of the settings can now be overridden on projects. This enables to have a default behavior and then specific configuration for projects without having to amend poms.
Read the rest of this page »
It is almost a tradition now : every month, we release a new version of Sonar. I am sure you are impatient to know which killing functionality is gonna be in version 1.9… Well, this month the new features are going to be difficult to show through screenshots… Read the rest of this page »
We’re happy to announce the availability of April’s release : Sonar 1.8. This new version, ready to go into production, contains several improvements and bug fixes. Here are the most important of them in screenshots :
This service enables at any level (project, module or package) to display the classes that have the most… and the less… Moreover, we are introducing a new metric that compounds code coverage and complexity of the class. This new metric’s objective is to highlight the classes to work on when you want to quickly increase your code coverage.
Read the rest of this page »
Sonar 1.7 has been released. This new version contains several improvements among which a much better compatibility with IE 6. On top of this, Sonar 1.7 has new features :
Most of the time, there is no need to evaluate generated sources. It is now possible to exclude them from analysis.

Need to know which tests failed and why ?

The functionality was already available at project level : it has been extended to modules and packages.

For more information, you can read the full release notes.
Sonar 1.6 has been released. On top of various bug-fixes and several improvements, it contains 3 new major features related to the management of quality profiles.
It is now possible to define thresholds and to trigger alerts on metrics, for example if the code coverage is less than 35% or if complexity by class is greater than 40… On any metric, there are two levels of thresholds : warning and error
We have taken a few screenshots of the next release, just to make you want to try the 1.5 release candidate 1 !
The Code Coverage report shows which lines of code were hit – or not – by unit tests. It works whatever the selected coverage tool, Cobertura (by default) or Atlassian Clover.

Simply visualize kinds of coding rules violations.


Mix complexity and code coverage measures to graphically discover which classes are the most risky. Big red classes are the most complex and the less tested.

Search coding rules by name, plugin, activation level or category. Results can be exported in CSV format. Did you notice the name of the plugin selected in the screenshot ? Yes, it’s well-known Findbugs, integrated besides Checkstyle and PMD.

Quickly access to project dashboards. The search bar is always accessible from the header. Just start typing the name of the project you search.


Compare trends of any measures on the same chart, for example to see if code coverage is related to complexity.

Simplify the Clover configuration, just copy the Clover license once in sonar and it will be available to all of your projects.
