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 »

The Groovy-Eclipse team is proud to announce the release of Groovy-Eclipse 2.7.0. This is the first release that includes Groovy 2.0 final and that is available on Eclipse 4.2 (Juno).  Now that Eclipse 4.2 is released, we will be dropping our Eclipse 3.6 support.

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

Groovy-Eclipse update site for Eclipse 4.2, 3.7, and 3.6


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:

Zipped Groovy-Eclipse update site for Eclipse 4.2, 3.7, and 3.6


For Eclipse 4.2:

For Eclipse 3.7:

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.


@TypeChecked Support

@CompileStatic Support


Groovy-Eclipse 2.7.0 includes Groovy 1.8.6 by default. Groovy 1.7.10 can be enabled optionally, and Groovy 2.0.0 can be installed through the extra compilers section on the update site.

This version of Groovy-Eclipse is recommended to be installed on STS 2.9.2, STS 3.0.0.M3, Eclipse 3.7.2, or Eclipse 4.2.  There is also a 4.2-based Groovy-Eclipse now available.  See above for the update site.

Bug fixes

See the details on our issue tracker.

What's next?

We are tentatively 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!

  • No labels