-0
I don't necessarily object, but my preference would be to see the
underlying issue fixed. Why is it a problem to locate the mojo now?
Given it is project centric, I would expect to add the plugin
definition to the build - in the same way that the Jetty plugin does,
for example. This has the advantage not only of then being able to
find goals from the command line, but locking the version down for a
reproducible build (probably not a concern for sonar in the historical
build scenario, but certainly for making sure different users get the
right version of the plugin).
Note that if it is moved to Mojo, are you intending to change the
license from LGPL?
Thanks,
Brett
On 07/04/2009, at 3:34 PM, Dan Tran wrote:
sounds reasonable, as long as the plugin has an active owner
+1
-D
On Mon, Apr 6, 2009 at 9:54 PM, Arnaud HERITIER
<[email protected]> wrote:
I think it is to be in the mojo groupId which doesn't requires extra
settings to use the short syntax
On Tue, Apr 7, 2009 at 4:10 AM, Dan Tran <[email protected]> wrote:
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
--
Arnaud
---------------------------------------------------------------------
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
