Anyone mind if I merge my script-maven-plugin into the groovy-maven-
plugin and prepare the groovy-maven-plugin for a release?
Docs for script-maven-plugin are currently here to review:
http://geronimo.apache.org/maven/genesis/plugins/script-maven-
plugin/index.html
The script-maven-plugin provides some additional support for
executing groovy scripts, including:
* Script source support, can be inline, local file, or URL
* Defines pom, project and log as default binding variables
* Allows script to be executed with a custom set of artifacts
appended to the classpath
* Allows script to have a custom script path, to include other
groovy classes
* Supports easy access to properties, and defaults which allows
easy cli overrides (like how ant -D works)
* * *
The only real issue, is that the script-maven-plugin depends on
classes on genesis' plugin-support module, which contains helpers for
things like artifact resolution. But I can always unroll those
dependencies, or re-create a new plugin-support module in the mojo
project.
Anyways, I think that the groovy execution support I have in the
script-maven-plugin is a vast improvement over the groovy-maven-
plugin, and I'd like to merge these plugins into one.
Any comments?
--jason
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
