Sonar 2.6 Adds Continuous Inspection Support for Ant Community
The Sonar team is proud to announce Sonar version 2.6. It is a tradition that we publish screenshots along with such an announce but for this one time, as the innovation is not "showable", we will make an exception !
Prior to 2.6, Sonar had a very tight link with Maven because we leveraged Maven technology at project inception to get a Bootstrapper that was cheap to implement and simple to use. Indeed, you could analyze a project by running "mvn sonar:sonar" on any project, just having to write a small pom.xml to point source directory on non-maven projects. This kind of dream for Maven projects was sometimes considered as a nightmare by the ANT guys due to the pre-requisite of installing Maven.
We thought it was time with Sonar 2.6 to refactor the bootstrapper mechanism to remove its tight coupling with Maven. It is now very simple for projects that are not built with Maven to run Sonar analysis and of course we have made sure there is no impact for existing Maven ones.
Along with the new release, we have published a Sonar Ant task and a Sonar Standalone Runner. Next step is to help the Gradle community to have their own Sonar runner (see GRADLE-888).
So what does it mean to use the Sonar Ant task ? Something very simple and standard :
- Download the Sonar Ant task
- Update your Ant build script
- Launch "ant sonar"
- Be ready to improve quality
To get more information, see the documentation page. Our goal is to give as many power to the Ant users than to the Maven guys. So we've already started to work on the Sonar Jacoco plugin to be able to automatically launch unit tests from the Sonar Ant task in order to compute code coverage measures. Stay tuned, this feature should be available quickly.
The full content of Sonar 2.6 is available in the release notes. Please do not forget to read the install or upgrade guides. You are now ready to download the new version and enjoy it ... with Ant if you want !