Folks, I've just released (after a wee fight with the release plugin) the latest and greatest Maven 2 Groovy integration modules.

This release contains above all other fixes and improvements... support to *implement* Maven 2 plugins in Groovy! The integration is... er... well, mostly seamless ;-) It works for the most part just like the Java bits do, only they are Groovy... and thus tax your fingers less, and delight your mind more (ie. closures, Groovy JDK, AntBuilder, etc) when you have to slave away creating them for man. And you can use Java mojos with Groovy mojos and get on your cross- mojonation if you fancy a swing that way too ;-)

I wrote up a quick little guide in the same manner as the other mojo development guides to help folks get going:

http://mojo.codehaus.org/groovy/guide-groovy-plugin- development.html

A few other significant changes, first several modules were added to support all of this, and thus I've moved them all into their own groupId:

    org.codehaus.mojo.groovy

You will need to update your projects to pick up this change. Also related to this change, the main site URL has been changed to:

    http://mojo.codehaus.org/groovy

And lastly, the syntax of the groovy:execute configuration of <source> has changed slightly. The new style does not required a <body>, <file> or <url> nested element to determine the source type, the plugin will figure it out. The old style is still supported, but will spit out a WARNING and the old style configuration will probably be dropped in future releases. See the execute examples for more details:

http://mojo.codehaus.org/groovy/groovy-maven-plugin/examples/ executing.html

Peep over the rest of the release notes below for other fixes, changes and improvements.

 * * *

Release Notes - Maven 2.x Groovy Plugin - Version 1.0-alpha-3

** Bug
* [MGROOVY-29] - Property resolving in the 'project' delegate is not working correctly when run from the Maven reactor * [MGROOVY-40] - The groovy plugin.xml extractor parses out .java and .groovy mojos, which causes duplicate conflicts

** Improvement
    * [MGROOVY-24] - When maven.test.skip=true skip groovy:testCompile
* [MGROOVY-28] - Re-package all Groovy modules into org.codehaus.mojo.groovy * [MGROOVY-30] - Fix dependency injection of the plexus GroovyComponentFactory
    * [MGROOVY-31] - Add ant = new AntBuilder() to groovy:execute
* [MGROOVY-32] - Maven ${} resolution of inlined Groovy scripts is causing problems with GStrings * [MGROOVY-33] - Allow optional handling of AssertionError (which is produced by Groovy's assert keyword) to omit evil stacktrace * [MGROOVY-34] - Hook up to the Plexus/Maven ExpressionEvaluator muck for property expansion
    * [MGROOVY-36] - Hookup AntBuilder's output to Maven's plugin Log
* [MGROOVY-37] - Create plugin development guide for implementing plugins in Groovy * [MGROOVY-41] - Don't use the metadata parser for .java sources, the Groovy Java parser seems to choke on some valid syntax

** New Feature
    * [MGROOVY-1] - Support mojo plugin.xml generation for Groovy mojos
    * [MGROOVY-26] - Add an archetype for groovy-mojo projects
* [MGROOVY-27] - Split up the mojo support from the compilation/ execution support
    * [MGROOVY-35] - Add fail() helper to GroovyMojoSupport

I've also updated the page on the Groovy site too with these details and updated the examples:

    http://groovy.codehaus.org/Groovy+Maven+Plugin

Please file bugs if you find one, or a enhancement request if you have one of those too:

    http://jira.codehaus.org/browse/MGROOVY

This is probably going to be the last of the alpha releases, unless something pops up (of course), the next release is slated for 1.0- beta-1. Which means its starting to solidify. If you have any significant changes you'd like to see to the 1.x serious, please lemme know soon.

Okay, enjoy!

--jason

PS. No fembots or sharks with freakin' laser beams attached to their heads were hurt in the release of these modules... oh ya... groovy baby!


---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to