Sonar in the news

by olivier gaudin|

    Welcome to the roundup of blog posts and pages that mentioned Sonar last month…



    Sonar and Gradle Multi-Module Projects
    By Gunnar Hillert, 13 January 2012

    I love Sonar. It is a wonderful way to collect some metrics for your Java projects - hassle-free and wrapped in a sweet-looking UI. For Maven-based projects Sonar literally works out of the box. Just start up your Sonar instance (assuming you are using the default settings running on localhost) and then you simply fire it off using:



    Measuring Code
    By David Green, 2 January 2012

    How good is your code? If you’re like the other 80% of above average developers, then I bet your code is pretty awesome. But are you sure? How can you tell? Or perhaps you’re working on a legacy code base – just how bad is the code? And is it getting better? Code metrics provide a way of measuring your code – some people love ‘em, but some hate ‘em.



    Making a Business Case For Using Codehaus Sonar
    By Chris Khoo, 6 January 2012

    Augmenting the development process is often a hard sell – processes don’t contribute directly to company profits and there are financial and time costs (for integration and maintenance) to consider. Personally, I’m a firm believer in adopting processes on an as-needed basis rather than trying to build the ultimate workflow/process all at once.



    Couverture des tests d’intégration avec JaCoCo, Maven et Sonar
    By Jean-Christophe, 23 January 2012

    Dans nos projets on rencontre souvent ce cas de figure : certaines portions de code se prêtent mal au test unitaire. Ce sont les interfaces graphiques, le code qui manipule des fichiers, les connexions réseaux… Cela peut poser problème lorsqu’on …



    Continuous Integration and Testing
    By John Dobie, 16 January 2012

    How do you know if using code metrics really does help to produce code with fewer bugs.
    I am convinced they do, but how can I possibly prove it? All projects have historic data. This is usually stored in your bug tracking and source code control tools. We can use the data stored in these systems to perform ‘code forensics.’ We use the historic data from real issues to see if they could have been avoided.