[
http://jira.codehaus.org/browse/MGROOVY-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111405
]
Joerg Schaible commented on MGROOVY-80:
---------------------------------------
Since it *is* in {{groupId org.codehaus.mojo.groovy}} instead of
{{org.codehaus.mojo}} the call to {{mvn groovy::shell}} does not work out of
the box.
{quote}
This issue is about fixing that, which I have done be creating a tiny plugin
which depends on the real plugin and copies its plugin.xml.
{quote}
Well, the headline for this issue is to setup a relocation. This means normally
a simple [relocation
POM|http://maven.apache.org/guides/mini/guide-relocation.html], that's what the
term "relocation" is normally used for in Maven land. You would have to create
such a relocation POM for every release if it had been your solution.
Your tiny plugin solution is something completely different, but I doubt that
anyone else would have thought of it by simply reading the description of this
issue ;-)
> 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
