is there a reason why sonar plugin could not stay with sonar project? Or this is the move for the entire sonar to mojo?
As I recall, we all recall to move plugin to the right place ( ipack plugin to izpack, jaxws to java.net, dbunit plugin to dbunit at sourceforge, etc ) -Dan On Mon, Apr 6, 2009 at 10:38 AM, Olivier Lamy <[email protected]> wrote: > +1 > -- > Olivier > > 2009/4/4 Simon Brandhof <[email protected]>: >> Hi, >> Sonar is a project hosted at Codehaus[1]. To make it quick, it's an advanced >> dashboard of code analysis metrics. >> It's composed of a web application - connected to a database - and a maven >> plugin, in charge of executing analysis plugins like JavaNcss, Checkstyle or >> Cobertura. This maven plugin is only a bootstrapper, it downloads sonar >> plugins from the server then executes them. Measures are consolidated and >> published on server-side. The current maven id is >> org.codehaus.sonar:sonar-maven-plugin. >> Integrate the maven plugin to the mojo project would make sonar installation >> easier. And it would be also a good complement to current reporting mojos, >> particularly maven dashboard [2]. All the more reason that they're not >> direct competitors. They don't apply to the same enterprise environments. >> >> If it's accepted a mojo-comptatible version of sources [3] will be published >> (maven documentation, package). >> >> Regards, >> >> Simon >> SonarSource.com >> Twitter : SonarSource / SimonBrandhof >> >> [1] http://sonar.codehaus.org >> [2] http://mojo.codehaus.org/dashboard-maven-plugin/ >> [3] http://svn.codehaus.org/sonar/trunk/sonar-maven-plugin >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
