Hi Aleksey, The mojo is a simple bootstrap over the org.codehaus.sonar maven plugin. End users should execute the first one. The latter is for internal use. The goal is to simplify the maven command, indeed the mojo version does not change when sonar is upgraded.
To sum up : you just have to focus on the command "mvn org.codehaus.mojo:sonar-maven-plugin:1.0-beta-2:sonar" or on its shortcut "mvn sonar:sonar". It works for any versions of sonar. This is explained in this post : http://www.sonarsource.org/we-had-a-dream-mvn-sonarsonar/ Regards Simon On Tue, Sep 14, 2010 at 11:00 AM, Aleksey Didik <[email protected] > wrote: > Hello. > > Could anyone tell me the difference between > org.codehaus.*mojo*::sonar-maven-plugin and > org.codehaus.*sonar*::sonar-maven-plugin? > > Looks like I have lost a little. > > Thanks, > Aleksey. > > > 13.09.2010 19:24, Simon Brandhof пишет: > > The Mojo team is pleased to announce the release of Sonar Maven Plugin, >> version 1.0-beta-2. >> It makes configuration easier when using a repository manager like Archiva >> or Nexus. Indeed no additional settings are required anymore ! Let's >> remind >> that the version 1.0-beta-1 needs to declare a mirror in maven settings. >> >> This improvement requires Sonar 2.2+. It is automatically disabled when >> using sonar 2.1 or less. Upgrading to this version should be automatic if >> the shortcut "mvn sonar:sonar" is used. >> >> Simon Brandhof >> >> >
