On 4/6/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Folks, I'd like to remove the mojo-sandbox/groovy-maven-tools tree. This currently contains:groovyc-maven-plugin groovymojo-maven-archetype javalike-maven-plugin-tools Groovy compilation is covered by the groovy-maven-plugin's compile and testCompile goals, which makes groovyc-maven-plugin uneeded. I plan on adding an archetype for Groovy mojo support, which will probably be copied from groovymojo-maven-archetype. And the javalike-maven-plugin-tools was created to help generate Mojo plugin.xml descriptors for .java and .groovy sources, which I have implemented in the groovy-maven-plugin, using the Groovy CST compiler API to process the language element correctly (the javalike needs some extra ';' inserted to properly find fields).
I don't use them so +0 but shouldn't you remove them once all the code has been moved into their new appropriate locations ? Not sure if there are users, but if i was a user, I'd rather have a working alternative in place. Cheers, Jerome --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
