[
http://jira.codehaus.org/browse/MGROOVY-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111366
]
Joerg Schaible commented on MGROOVY-80:
---------------------------------------
I fear this was a bad idea. As you already stated yourself, you have to add the
groupId to settings.xml now, while it worked OOTF before (as all other Codehaus
Mojos do). Additionally the relocation only is considered, if Maven has reason
to look at the old location. If people start to use the new groupId in their
POMs, Maven will no longer download the relocation POM. I am not sure, if it
will work implicitly by calling
mvn groovy:shell
just because Maven looks by default in the org.codehaus.mojo groupId, but even
if it does, you will have to provide *always* for any release a relocation POM
in future.
> Setup a relocation for the groovy-maven-plugin
> ----------------------------------------------
>
> Key: MGROOVY-80
> URL: http://jira.codehaus.org/browse/MGROOVY-80
> Project: Maven 2.x Groovy Integration
> Issue Type: Improvement
> Components: build
> Reporter: Jason Dillon
> Assignee: Jason Dillon
> Fix For: 1.0-beta-3
>
>
> A while back I move the groovy-maven-plugin from org.codehaus.mojo to
> org.codehaus.mojo.groovy, mostly because the groovy integration became more
> complex and required multiple modules so I put them all into their own
> groupId. But this had the side affect of not allowing users to use the
> 'groovy' prefix w/o adding configuration to their settings.xml to search the
> new groupId. So, when users try things like:
> {noformat}
> mvn groovy:execute
> {noformat}
> ... they end up with the old version of the plugin. So we need to setup a
> relocation to allow that usage to work correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
