+1
--jason

On Nov 28, 2007 11:56 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:

> Hi folks, its me again... this time with some super-fabulous uber-ass-
> kicking Groovy integration for Maven updates for your building pleasure.
>
> This is a significant release, as I rewrote a bunch of the internals
> to allow the version of the Groovy runtime to be pluggable, thus
> allowing the plugin (and friends) to support Groovy 1.1 AND Groovy
> 1.0, and probably any version to come in the future (maybe, I hope).
> By default the plugin will select the *default* runtime, which will
> probably always be the latest supported version of Groovy (1.1-rc-3
> ATM).
>
> Another very significant update is a fix for that evil URI pat problem
> that folks have been hitting on Windows (BTW, get a Mac already).  A
> bunch of other bits have been fixed, added, blah, blah.
>
> This version has a re-implemented joint/mixed complication mode, which
> as a nice side effect allows the basic maven-javadoc-plugin to be used
> to generate a joint/mixed API doc.
>
> With the new runtime abstraction muck I did sacrifice a few bits,
> which I figure no one uses anyways, for the moment.  So these bits are
> not gone for the time being:
>
>  * java2groovy
>  * groovydoc (use the javadocs stuff na)
>
> For the complete list peep over the release notes:
>
>  * * *
>
> Release Notes - Maven 2.x Groovy Integration - Version 1.0-beta-3 **
> Bug * [MGROOVY-64] - Invalid dependency path on Windows * [MGROOVY-81]
> - Repository pom containing dependencies with ${pom.version} *
> [MGROOVY-94] - Embedded Groovy script returns null for variables and
> expressions * [MGROOVY-97] - compulsory groovy folders * [MGROOVY-100]
> - Custom/patched Ant 1.7.0 does not include all classes which are in
> the original jar ** Improvement * [MGROOVY-67] - Use the groovy-all-
> minimal artifact + dependencies * [MGROOVY-68] - Remove usage of the
> org.codehaus.mojo:plugin-support dependency * [MGROOVY-75] - Add
> incremental compilation support to only compile when sources have
> changed * [MGROOVY-79] - Create a new stub generator which includes
> Javadocs so we can reuse the javadoc plugin to create aggregate API
> docs * [MGROOVY-80] - Setup a relocation for the groovy-maven-plugin *
> [MGROOVY-82] - Allow to compile against groovy-1.0 * [MGROOVY-83] -
> Upgrade to Groovy 1.1-beta-3 * [MGROOVY-84] - Add support to invoke
> the "new" groovysh cli shell * [MGROOVY-86] - Add a Groovy runtime
> abstraction layer to allow the version of Groovy used to be pluggable
> * [MGROOVY-88] - Add support to optionally sanitize Groovy stacktraces
> * [MGROOVY-89] - Upgrade groovy-runtime-1.1 to Groovy 1.1-rc-1 *
> [MGROOVY-93] - Rename GroovyMojoSupport to GroovyMojo * [MGROOVY-95] -
> Upgrade shitty-maven-plugin to 1.0-alpha-1 * [MGROOVY-96] - Upgrade
> cobertura-maven-plugin to 2.2 * [MGROOVY-99] - Upgrade to Groovy 1.1-
> rc-3 ** New Feature * [MGROOVY-48] - Generate groovy plexus components
> descriptor ** Task * [MGROOVY-71] - Setup code coverage reports *
> [MGROOVY-77] - Add documentation for how to use the mixed Java +
> Groovy compile bits * [MGROOVY-91] - Remove the groovydoc goal *
> [MGROOVY-92] - Remove the java2groovy goal
>
>  * * *
>
> This release has a bit of complication as it depends on SHITTY, and
> SHITTY depends on it. Also ATM its using a SNAPSHOT of cobertura-maven-
> plugin.  I will release this and SHITTY at the same time to resolve
> the first, and if cobertura-maven-plugin 2.2 isn't out when its time
> to release I will simply disable that report.
>
>  * * *
>
> So lets do the number plusy/minusy thingy already...
>
> [_] +1  I have only one thing to say... "I love the groovy+maven
> integration, bring it on"
> [_] +0  Um, my afro is still blowing out... so I'm not so groovy just
> yet, but I got my dancing shoes on
> [_] -1  Disco is dead man... oh crap my polyester body suite is on
> fire... wait... no... don't release it...
>
> Please vote... I'll wrap this up in about 73 hrs or so, depending on
> if my cold gets better or worse by then.
>
> Cheers,
>
> --jason
>
>
>

Reply via email to