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:
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:
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 indent 10px maxLevel 4 style disc
Groovy 2.0 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.0.4, which uses Groovy 1.8 as its compiler. When Grails moves to being based on Groovy 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.
Maven integration with
The groovy-eclipse-compiler plugin for maven has just released the 2.7.0-01 version and now uses Groovy 2.0 to compile against by default. You can specify other Groovy compiler levels if required. See Groovy-Eclipse compiler plugin for Maven for more information.
@TypeChecked and @CompileStatic Support
With the 2.0 compiler enabled, you can use the
@CompileStatic annotations and Groovy-Eclipse compiles with them appropriately. Here is an example from the What's new in Groovy 2.0 article on InfoQ:
Also, reconciling (i.e., eager parsing as you type) handles these annotations properly. So, you get proper affordance when changing
int object = new Date() to
Date object = new Date():
Assign statement to new local variable quickfix
The Groovy-Eclipse editor now provides a new quickfix for assigning a statement to a local variable. To access the quickfixes, press CTRL/CMD+1. Choose Assign statement to new local variable:
And the results look something like this:
Convert variable to field
Groovy-Eclipse now provides a refactoring to convert local variables to fields. To access the refactoring, select a local variable:
In the context menu, choose Refactoring --> Convert Local Variable to Field...
A wizard pops up where you can tweak your options and preview the results:
Note that not all options are implemented yet. Unimplemented pieces of the refactoring wizard are grey. After pressing OK, you will see something like this:
Doc hovers with @link and @see
Doc hovers now respect the
@see JavaDoc tags, so you can add them to your DSLDs and users will be able to follow proper links to other parts of the source code:
Source code to github
Groovy-Eclipse is now on GitHub. Forking and pull requests are appreciated!
The old SVN repository is no longer valid.
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.
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.