Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Groovy-Eclipse team is proud to announce the release of Groovy-Eclipse 2.7.1. This is a service refresh of Groovy-Eclipse and it now contains support for the 2.0.4 Groovy compiler as well as Eclipse 4.2.1 and 3.8.1.

You can use the following update sites to install this release:

titleGroovy-Eclipse update site for Eclipse 4.2 and 3.7

For Eclipse 4.2 (Juno):

For Eclipse 3.7 (Indigo):


The Groovy 2.0 compiler is not installed by default.  If you want to install it, you can do so from the Extra Compilers category in the update site.

And a zipped version of the update site is available at:

titleZipped Groovy-Eclipse update site for Eclipse 4.2 and 3.7

For Eclipse 4.2 (Juno):

For Eclipse 3.7 (Indigo):

You can install from the zip by pointing your Eclipse update manager to the downloaded zip file and following the installation instructions.  Do not unzip into your Eclipse dropins folder.

Table of Contents

Groovy 2.0.4

Groovy 2.0.4 is now available in Groovy-Eclipse as an optional add-on.  We have not yet made the compiler default because we make our default compiler compatible with the default compiler of the latest release of Grails.  At the time of this release, Grails is at version 2.1.1, which uses Groovy 1.8 as its compiler.  When Grails moves to being based on Groovy 2.2.x, Groovy-Eclipse will move its default compiler as well.

To install Groovy 2.0, go to Help --> Install new Software.  In the work with tab, choose the Groovy-Eclipse update site and select the Extra Compilers category:

Read Compiler Switching within Groovy-Eclipse for more information on how to install Groovy 2.0 and how to switch compiler levels.

Eclipse 4.2.1 and 3.8.1

We have updated the JDT feature patch to be based off of JDT version 3.8.1, which is the version used in Eclipse 4.2.1 as well as 3.8.1.

Add project-level warning if compiler levels don't match

There is now a project setting that records the last compiler level that compiled it.  You can access this setting in the Groovy Compiler settings page for the project:

This is in addition to the workspace compiler level, which is found at Preferences -> Groovy -> Compiler:

If the compiler level for the project is different from that of the workspace, then an error marker is placed on the project and it cannot be built until the compiler levels are resolved:

To resolve the marker discrepancy,  select the marker or markers that you want to fix, and you can choose one of three ways to resolve the conflict:

You can choose to:

  1. Configure the compiler level for the project(s), which opens a dialog where you can manually choose a compiler level
  2. Change the compiler level for the entire workspace (i.e., change which compiler is being used in the workspace).  This requires a restart.
  3. Or simply set the project compiler level to match the workspace compiler level.  Most of the time, this is the option you will want to choose.

Better Content assist for Annotation

Content assist in the context of an annotation, will only show annotations, not classes, interfaces, or enums:


Groovy-Eclipse 2.7.1 uses Groovy 1.8.6. Groovy 1.7.10 can be enabled optionally, and Groovy 2.0.4 can be installed through the extra compilers section on the update site.

This version of Groovy-Eclipse is recommended to be installed on STS 3.0.0, STS 3.1.0.RC1, Eclipse 3.7.2, 3.8.1, and 4.2.1.

Bug fixes

See the details on our issue tracker.

What's next?

We are planning a 2.8.0 release in October. You can take a look at all issues we are planning to fix for this release.

We appreciate all community support and feedback. If you wish to join the discussion about Groovy-Eclipse then please sign up for the mailing list. For any issues you have (or enhancements you would like to see), please raise them in our issue tracker. If there is an existing bug fix or enhancement that you require are not seeing any movement on, please make some noise on it (and get your friends to do the same). We respond to community feedback, and we can make the most improvements to Groovy-Eclipse when we hear directly from the community. So, please speak up.