Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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.

How to use the compiler plugin---Setting up the POM

Here are the required additions to your maven project's pom.xml to use the compiler plugin. The artifacts are currently in the SpringSource snapshot maven repo. You must add it as a regular repository:

as well as a plugin repository:

And 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 groovy-eclipse-batch artifact):

This will allow Groovy files to be compiled. The maven-compiler-plugin prefers all source files to be in src/main/java and src/test/java, but if you prefer you can use the standard Groovy convention and keep your files in src/main/groovy and src/test/groovy. You can do so by adding the following plugin to your build section of the pom:

The information in this section was adapted from the Contraptions for Programming blog.

Sample project and source code

A sample project using the compiler plugin as well as the source code for the plugin itself are available from the subversion repository:


The repository URL is:

There are several projects in the repository:

  • groovy-eclipse-compiler : the compiler plugin itself (an m2eclipse project).
  • groovy-eclipse-batch-builder : a set of ant scripts and configuration files used to build the groovy-eclipse-batch artifact. This artifact is an amalgamation of all jars required for compiling Groovy and Java code in Eclipse, including ecj (the Eclipse compiler for Java), the non-UI components of Groovy-Eclipse, the Groovy jars, and various required Eclipse bundles.
  • groovy-eclipse-maven-tests : a sample project that uses the compiler plugin (an m2eclipse project).
  • org.codehaus.groovy.m2eclipse : an Eclipse plugin that provides integration between Groovy-Eclipse and m2eclipse (the Maven tooling for Eclipse).
  • Feature org.codehaus.groovy.m2eclipse : an Eclipse feature that is required for building and releasing the org.codehaus.groovy.m2eclipse plugin.

We don't have a maven archetype project available for the compiler plugin. We would greatly appreciate someone contributing one.

M2Eclipse integration

Groovy-Eclipse also provides integration with m2eclipse, the Eclipse's tool support for Maven. Using this integration will ensure that your GEM projects will be properly configured when they are imported into Eclipse. You can install the integration from the following update site:

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:

  1. 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.
  2. The Groovy-Eclipse compiler is the same inside Eclipse and inside Maven, and so configuration across the two platforms can be simplified.
  3. 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:

  1. Only one compiler level is supported. This is currently Groovy 1.7.5. If you require a different version of Groovy, then GMaven is your only option.
  2. GroovyDoc tool is not supported because the compiler plugin does not produce stubs.
  3. Groovy Mojos are not supported.

Whether or not the Groovy-Eclipse compiler plugin for Maven is appropriate for your project will depend on your requirements.

Where to find more information and ask questions


Please ask all questions on the Groovy-Eclipse mailing list. Any bugs or feature enhancements should go on Groovy-Eclipse's jira.

The compiler plugin was originally described here and here, but these posts are no longer updated and this page will always contain the most recent information.

  • No labels