For Eclipse 4.3 (Kepler):
For Eclipse 3.8 and 4.2 (Juno):
For Eclipse 3.7 (Indigo):
We have repackaged the org.codehaus.groovy bundles and removed extraneous jar files. Install size of Groovy-Eclipse has been reduced by about 20 Mb.
Better formatting of compiler messages
Compiler messages from the groovy-eclipse-compiler are now proper Maven log compiler messages. This means that you can now suppress compiler warnings by using
<showWarnings>false</showWarnings> in the configuration of the maven-compiler-plugin.
Now requires explicit groovy-eclipse-batch dependency
The 2.8.0-01 release of the groovy-eclipse-compiler (the Eclipse-based Groovy compiler plugin for Maven) has been released simultaneously with Groovy-Eclipse 2.8.0. The groovy-eclipse-compiler artifact is a small wrapper that implements the compiler plugin API. Actual compilation is delegated to the groovy-eclipse-batch compiler. There is a version of the groovy-eclipse-batch artifact for each Groovy version. Prior to 2.8.0-01, consumers did not need to explicitly specify a groovy-eclipse-batch version in the pom. In this case, the most recent version of groovy-eclipse-batch was used. However, this lead to problems when a new version of groovy-eclipse-batch was released and the behavior of builds would change. Now, the version must be explicit and this ensures stability of builds over time. For example, running with the following will produce an error message: