Relocating plugins?

[Jason Dillon <ja...@planet57.com>]

Can the <distributionManagement>'s <relocation> element be used to  
relocate a plugin?

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:

     mvn groovy:execute

... they end up with the old version of the plugin.

Is it possible to use the <relocation> support to get mvn to  
internally redirect the above to the new groupId?  Or will that only  
work for dependency artifact resolution and not for plugin execution?

I had considered moving just the groovy-maven-plugin back to the  
org.codehaus.mojo groupId to get around this, though then I'd have  
the same problem with folks using the org.codehaus.mojo.groovy  
groupId in their poms for the g-m-p.  So either way I need to get  
some kind of relocation to work.

Does anyone know what the best solution is here?

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org