The 2.5.1 release is about a month after the 2.5.0 release, which as been a shorter release cycle than normal. Because of this, there have been fewer enhancements compared to previous releases. That being said, we have focussed on our DSL descriptor support: fixing a few bugs, increasing performance, and ensuring that some standard DSLDs are available on install.
You can use the following update site sto install this release.
And a zipped version of the update site is available at:
You can install from the zip by pointing your Eclipse update manager to the downloaded zip file and following the installation instructions.
groovy-eclipse-compiler for Maven
We have released the groovy-eclipse-compiler for Maven that let's you use the Groovy-Eclipse compiler in your maven projects. This provides a more robust way of compiling mixed Groovy-Java projects with Maven than previous approaches have allowed. See all the documentation at the Groovy-Eclipse compiler plugin for Maven page.
DSL Descriptor enhancements
We now make it easier to use and share DSLD files in the workspace.
There is a
Multiple DSLDs of same name
Disabling DSLD support
What to expect for the future of DSLDs
Built-in AST transforms recognized in the editor
Groovy-Eclipse 2.5.1 includes Groovy 1.7.10 by default. Groovy 1.8.0 can be optionally installed. Groovy-Eclipse is installable on STS 2.7.0, Eclipse 3.7.0, 3.6.0, 3.6.1, or 3.6.2. There are different update sites for Groovy-Eclipse targeting Eclipse 3.6 and 3.7. See above for the update sites.
There have been 30 bug fixes in this release. You can see all of them in the Codehaus issue tracker.
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!