+1
About the archetype, please put in into (at choice)
- mojo-archetypes
-mojo-sandbox/mojo-archetypes
Regards,
Raphaël
2007/4/6, Jason Dillon <[EMAIL PROTECTED]>:
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).
* * *
Anyways, I don't think we need to keep these modules around anymore.
Does anyone object if I remove them?
--jason
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
