Groovy-Eclipse provides a compiler plugin for Maven. Using the compiler plugin, it is possible to compile your maven projects using the Groovy-Eclipse compiler.
Groovy-Eclipse configurator for M2Eclipse
If you are going to be working with your maven project inside of Eclipse, it is strongly recommended that you install the Groovy-Eclipse configurator for M2Eclipse. The feature is currently available from the Groovy-Eclipse snapshot update:
Once Groovy-Eclipse 2.5.2 is released, the configurator will also be available from the release update site.
How to use the compiler plugin---Setting up the POM
In your plugin section, you must change the compiler used by the maven-compiler-plugin. Like the javac ant task, the maven-compiler-plugin does not actually compile, but rather delegates the compilation to a different artifact (in our case, the
By default, this will use Groovy 1.8.0 to compile your code. If you would prefer to use 1.7.10, then add another dependency to the maven-compiler-plugin:
This will allow Groovy files to be compiled. The maven-compiler-plugin prefers all source files to be in
src/test/java, but if you prefer you can use the standard Groovy convention and keep your files in
src/test/groovy. You can do so by adding the following plugin to your build section of the pom:
The groovy-eclipse-compiler recognizes all settings supported by the maven-compiler-plugin.
Note that the groovy-eclipse-compiler and groovy-eclipse-batch artifacts are now available in Maven-central, so there is no longer any need to explicitly declare any extra repositories.
Sample project and source code
There is an archetype available for this project. You can use it through a command like this:
A sample project using the compiler plugin as well as the source code for the plugin itself are available from the Codehaus.org subversion repository:
Why another Groovy compiler for Maven? What about GMaven?
There are several benefits that the compiler plugin provides over GMaven, but at the same time it has a few limitations. First, the benefits:
- The compiler plugin does not require the creation of Java stubs so that your Groovy files can compile against Java files. This will prevent some arcane compile errors from appearing.
- The Groovy-Eclipse compiler is the same inside Eclipse and inside Maven, and so configuration across the two platforms can be simplified.
- The compiler plugin is a standard compiler plugin for Maven. It therefore follows all allows all the same standard configuration that the Javac compiler plugin uses. This makes it simpler to introduce Groovy into an existing Maven project. All you need to do is change the compiler plugin that the pom references.
There are some limitations:
- GroovyDoc tool is not supported because the compiler plugin does not produce stubs.
- Groovy Mojos are not supported.
- Groovy scripts cannot be executed in your poms.
- Groovy compiler options are not passed through to the compiler.
defaultScriptExtensioncompiler option is not supported.
Whether or not the Groovy-Eclipse compiler plugin for Maven is appropriate for your project will depend on your requirements.
Groovy-Eclipse also provides integration with m2eclipse, the Eclipse's tool support for Maven. Currently, this support is only meant to be used with existing GMaven projects. It will have no effect on groovy-eclipse-compiler projects. If you want to use groovy-eclipse-compiler projects in maven, then you should use the maven-eclipse-plugin as described above.
Using this integration will ensure that your GMaven projects will be properly configured when they are imported into Eclipse. You can install the integration from the following update site: