The release 1.4.2 is available for download. It fixes two bugs :

• SONAR-344 Configuration of custom rules is not read when importing checkstyle.xml file
• SONAR-351 MySql broken pipe on inactivity timeout

Upgrade steps from 1.4.* releases are :

• unzip the distribution
• replace sonar-1.4.2/conf/, sonar-1.4.2/extensions/ and sonar-1.4.2/data/ directories by yours
• If MySql database, add the following property to sonar-1.4.2/conf/sonar.properties :
  sonar.jdbc.validationQuery: select 1
• start the server
• update the maven plugin version :
  mvn org.codehaus.sonar:sonar-maven-plugin:1.4.2:sonar

We’re pleased to sponsor and participate to * CITCON 2008  (Continuous Integration and Testing Conference) in Amsterdam. We will attend this conference for the first time and I’m a bit curious and looking forward to see how this technologic OpenSpace will behave with 150 expected participants.



It’s strange not to see Atlassian along with other sponsors like Anthillpro as they’ve just opened a new office in Amsterdam. I’d have been happy to meet guys from Atlassian to discuss about software quality and to know where they plan to go with the promising “Build Telemetry” feature integrated in Bamboo.



Since we have not been communicating much so far about young Sonar, this event is a good chance for us to start gathering feedback from the community.



* : “CITCON (Continuous Integration and Testing Conference) brings together people from every corner of the software development industry to discuss Continuous Integration and the type of Testing that goes along with it.“

As Sonar is an enterprise quality tool, it must scale well when number of projects and snapshots by project grow over time. We consider this capability to be a plain Sonar functionality. So we manage it as the others by launching regression tests on each new release and trying to tune performance from one release to the other.

Ok fine, but what means “scale” in Sonar’s context and what is the protocol used to measure this capability ? As a good coach, we decided to answer this question by asking new ones :

Read the rest of this page »

Sonar 1.4.1 is now available for download. This is a bug fix release that prevents failures when migrating from previous sonar releases on Oracle database. It also fixes some bugs on coding rules.
Thanks to Michel Pawlak, Matthias Flor and Martin Ehrnhoefer for their help.

The Sonar team is pleased to announce the release 1.4. This version is a bug fix release from version 1.3. We had a number of minor glitches that we felt were important to release. These include :

• coding rules improvements (upgrade to checkstyle 4.4, copy profiles, display name of tools, permalinks on XML export)
• fix a JavaNCSS bug when parsing Java5 annotations from method body
• startup scripts on specific linux/solaris plateforms
• fix bugs on IE6 and SQL Server database

Read the release notes for more details. Updating to this version is recommended. Don’t forget to read the migration guide for 1.2/1.3 users. It’s really simple but it’s mandatory to respect the procedure.

We also developed an extension to analyse PL/SQL projects. Contact us for more details.

Now that 1.4 has been completed, we are finalizing the plugins framework to easily extend Sonar measures. We’ll release a BETA API on 1.5. Other planned features are advanced details on sources (lines covered by unit tests. messages of test failures) and better time machine charts.

Thank you for all your feedback with making this a successful release !

We are pleased to announce that Sonar 1.3 is now released. The major feature is the dramatic improvements to stability and performance. Other features are :

• deploy as a WAR on Tomcat 5.5
• measures on Java packages
• more details on Java classes
• new measures : ratio of duplicated lines and ratio of comments

You will find documentation at http://sonar.codehaus.org/documentation/1_3/ and the distribution on the download page. You can also have a look at the full release notes.

Please stay tuned !

You’re interested in Sonar but you don’t want to loose your time with its installation (even if it’s really simple ;o) ? Just have a look at Nemo, our public instance of the last version of Sonar. This is a new experience for us, so let’s say it’s a BETA service. We will see if performance and stability are acceptable enough without increasing hardware resources.



For your information, measures are realized on some open-source projects we selected among those criteria : use of subversion/maven2 and successful compilation.



http://nemo.sonar.codehaus.org

The Sonar team is happy to announce the first Release Candidate of the version 1.3. If only one feature should be arrested, it would be the dramatic improvements to stability and performances. A benchmark will be published soon.

Other features are :

• deploy as a WAR on Tomcat 5.5
• measures on Java packages
• more details on Java classes
• new measures : ratio of duplicated lines and ratio of comments
• and bug fixes

You will find documentation at http://sonar.codehaus.org/documentation/1_3/ and the distribution on the download page.

Please give it a try to help us make Sonar as good as possible. All your feedbacks are welcome on the mailing-list.

Sonar 1.2.1 is now available. It fixes two bugs when using the embedded database, which is the default mode when installing sonar :

• SONAR-219, no chart on classes distribution by complexity
• SONAR-184, error on the rules breakdown page.

Just unzip the application without replacing the directories /conf, /data and /extensions.

We have always been impressed by the layout of the Google Analytics dashboard. Its data oriented interface is intuitive, simple and powerful at the same time. It gave us a lot of ideas to improve Sonar usability. The release 1.2 is the first step of this interface refactoring. For example major measures like code coverage or complexity/method are emphasized on the project dashboard.

The actual new feature of this release is reviews, like design or code reviews. They are a well-known technique to obtain quality and productivity improvements, even in agile teams. Resulting measures of such manual reviews are saved and displayed on the dashboard besides other metrics. Of course it does not replace tools like Atlassian Crucible, focused on the whole review process.

The release also fixes some bugs. Have a look at the changelog for more details. Download the application and read the installation guide for more details.

The development iteration is one month long, so the release 1.3 is planned for end of April. Until this time don’t forget the mailing-list to give your feedback !

The Sonar team