On Nov 28, 2007, at 11:59 PM, Arnaud HERITIER wrote:
Sorry for the delay of the reply.
You have my +100.
When a project want to host it, il always better to have the plugin
near to the project to have a better support.
Jason, don't forget that you'll have to create/maintain at least a
parent pom to reproduce settings that we have in the mojo project.
This parent pom could extended by your sub-project and also by
groovy core libs.
Yup, I know :-)
Another side effect is that you could/must have to use the groupId
org.codehaus.groovy which isn't a groupId recognized by maven as a
plugin groupId (by default).
Ya, which is balls IMO... but I have the magic ability to clone
plugins and give them new groupIds. Or does the 'Haus enforce
permissions on that stuff? ie. can I publish a shadow plugin to
org.codehaus.mojo from the Groovy project?
I guess that is a minor issue, though, this:
mvn groovy:shell
is certainly easier for folks than:
mvn org.codehaus.groovy.maven:groovy-maven-plugin:1.0-beta-3:shell
Well, I guess we'll find out.
Too bad the search path for plugin groupId's isn;t more dynamic/
flexible/friendly....
--jason
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
