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:
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:
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.
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.
See the details on our issue tracker.
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.