Last week, Simon Brandhof and Freddy Mallet of Sonar team and me were discussing Vaadin uses. At the end of our meeting, and although Vaadin finally did not fit their particular needs regarding Sonar, the talk disgressed toward quality. As regular Sonar users know, the former includes a very interesting plugin aptly named Technical Debt plugin. As a reminder: Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite
This week, I was tasked to create a development infrastructure with the following components: Subversion for Source Code Management, Trac for bugtracking, Hudson for Continuous Integration, Sonar for Quality Reporting, and Nexus, a Maven repository. I added 2 more components: a database in order to store data from each application in the same datastore, and a LDAP in order to authentify oneself in each application with the same credentials.
Sonar is a free OpenSource product that provides you with a general dashboard displaying information about the codebase of each configured project, such as: Number of failed tests,% of code coverage,% of rules compliance (more later),% of duplicated lines,and much more. Then you get an additional graphical information showing: a square for the size of your project’s codebase relative to the entire codebase’s size,a color (from red to green) for the % of rules compliance. Yet, w