> > 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 don't know. You can ask to Carlos. It's often him who administrates the repository > > > 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.... Yep, I hope it will evolve in the futur. One idea is to have the list of groupId in a metadata file stored in the root of the repository (and no more those horrible hardcoded values that are org.apache.maven.plugins and org.codehaus.mojo) > > > > --jason > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
