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:
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:
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:
Selectively Allow AST Transforms to run during reconciling (i.e., in the editor)
Groovy-Eclipse now recognizes a system property that describes which AST transforms should run during reconciling (i.e., in the editr while typing—all AST transforms run during a regular compile).
If this feature is popular and gets good feedback, we will allow the setting of the system property through a preference dialog and allow each project to use their own settings. Please vote on the issue at GRECLIPSE-XXXXXXX. (GRECLIPSE-1406)
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 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