Sonar 1.8 in screenshots
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 :
Hotspots
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.
Manage FindBugs configuration
It is now possible to import and export FindBugs XML configuration file as for Checkstyle and PMD (Thanks a lot to Jene Jasper for this major contribution).
Duplicated lines detection
It’s now possible to configure the number of consecutive tokens necessary to detect a copy/paste. By default, this number is 100,
Rules Compliance Index in clouds
The clouds service displays all classes of a project/module/package. By default, the size of a class depends on the cyclomatic complexity and the color on the code coverage. The color can now also depends on the Rules Compliance Index.
SONAR-222
The famous SONAR-222 has been fixed in this version. Despite the fact that it cannot be shown as a screenshot :-), we thought it was worth mentioning. Sonar does not use the maven embedder anymore. This has resolved a bunch of issues. For instance Sonar 1.8 is compatible with Maven 2.1.
For more information, you can read the full release notes.
The next check point is gonna be in May with Sonar 1.9 : JavaNCSS will be replaced by sonar-squid and performances should greatly improve (new JRuby on Rails, GWT 1.6 and database optimizations) !
Great stuff! Keep up the great work. Where are you guys using GWT? Are you using GWT for the front end and JRuby for the back end?
P.S. GWT rocks :)
By Arthur on April 23, 2009 at 5:32 am
GWT is an extension point used to develop pages like hotspots, clouds or source viewers. A plugin can define its own GWT pages.
JRuby on Rails is used for the layout, all core pages (dashboard, timemachine) and web services. It’s the best framework for us to develop pages quickly, but we did not want to give ruby extensions to community. It’s too hard to document and to maintain.
By Simon on April 23, 2009 at 10:48 am
Simon,
from your answer I take that Sonar supports Ruby, but that the ruby extension is not released, is that correct ?
Is there any plans to release it in the future ?
Thx
By Yacin on May 5, 2009 at 7:44 pm
Unfortunatly no. JRuby is used internally but there are no plugins to analyse ruby code. I don’t know ruby tools very much, do you know if there are some code analysers ?
By Simon Brandhof on May 6, 2009 at 8:14 am
Simon,
There are quite a few ruby code analyzers. Here are 3 that I use:
rcov (for code coverage): http://eigenclass.org/hiki.rb?rcov
flog (for code complexity scores): http://ruby.sadi.st/Flog.html
flay (for structural similarity): http://ruby.sadi.st/Flay.html
By Aaron Patterson on September 24, 2009 at 5:59 pm
You can vote for the issue SONARPLUGINS-81, updated with these tools. See http://jira.codehaus.org/browse/SONARPLUGINS-81
By Simon on October 1, 2009 at 7:19 am