I've just released version 1.0-alpha-2 of the groovy-maven-plugin.

This release fixes a few major issues with the groovy:compile and groovy:testCompile goals. Compilation goals now require that *all* dependencies be included on the classpath (aka added to the poms dependencies) and no longer pickup any classpath elements from the plugin's dependencies itself. This should resolve any issues where Groovy classes are dependent on other classes which are not included in the plugin's dependencies (like junit for example).

Additionally, you can now run `mvn groovy:compile` and `mvn groovy:testCompile` from the command-line and they will properly resolve and pickup dependencies for the proper scope. Please be aware that if you run these goals explicitly, that you must configure your poms to use the plugins configuration element and not a plugin execution configuration. I still recommend that for normal usage that folks hook up these goals to phases and specify a phase name on the command-line (aka `mvn install`). But, if you really want you can invoke the goals themselves too ;-)

Resolved issues:

[MOJO-702] - The compile and testCompile goals should use @requiresDependencyResolution for the proper scope
    [MOJO-699] - Add extra validation for fileset configuration
[MOJO-696] - groovy:testCompile fails to load junit classes when using GroovyTestCase as base-class

Site/documentation:

    http://mojo.codehaus.org/groovy-maven-plugin/

Artifacts published here:

http://repository.codehaus.org/org/codehaus/mojo/groovy-maven- plugin/1.0-alpha-2/

In a few hours these will be on central when the repo sync kicks in.

 * * *

Please use, enjoy and provide feedback if you like :-) Unless folks inform me of significant problems or recommend major enhancements, the next release will probably be 1.0-beta-1, and then soon after we will get to 1.0.

Thanks to everyone that has provided feedback so far, as well as patches!

Cheers,

--jason

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

   http://xircles.codehaus.org/manage_email

Reply via email to