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 2 Next »

Groovy-Eclipse provides a compiler plugin for Maven. Using this compiler plugin, it is possible to compile your maven projects using the Groovy-Eclipse compiler.

How to use GEM---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:

This will allow Groovy files to be compiled. The maven-compiler-plugin prefers all source files to be in

Unknown macro: {src/main/java}

and

Unknown macro: {src/test/java}

, but if you prefer you can use the standard Groovy convention and keep your files in

Unknown macro: {src/main/groovy}

and

Unknown macro: {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 Codehaus.org subversion repository:

Icon

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 GEM provides over GMaven, but at the same time it has a few limitations. First, the benefits:

  1. GEM 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. GEM is a standard compiler plugin for Maven and so it can be configured using the same simple configuration as the javac compiler plugin for Maven. http://maven.apache.org/plugins/maven-compiler-plugin/index.html It is therefore exceptionally easy to gradually introduce Groovy code into an existing project. All you need to do is change the compiler plugin that the pom references.

http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html

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 is not supported.
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

GEM was originally described in the following blog posts, but these posts are no longer updated and this page will always contain the most recent information.

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

  • No labels