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

Version 1 Next »

The Groovy-Eclipse team is proud to announce the release of Groovy-Eclipse 2.6.0. As usual, we have some exciting new features in this release, including quick fixes/quick assists, improved content assist, and improved search and refactoring. Groovy-Eclipse 2.6.0 includes 1.8.4 support as an optional add-on. Once Grails 2.0 is released officially, we will make Groovy 1.8.x the default compiler in Groovy-Eclipse.

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

Groovy-Eclipse update site for Eclipse 3.7 and 3.6

Icon

If you want the Groovy 1.8 compiler, you must explicitly include it by checking the "Extra compilers" category.

And a zipped version of the update site is available at:

Zipped Groovy-Eclipse update site for Eclipse 3.7 and 3.6

Icon

For Eclipse 3.7:
http://dist.springsource.org/release/GRECLIPSE/e3.7/XXX

For Eclipse 3.6:
http://dist.springsource.org/release/GRECLIPSE/e3.6/XXX

You can install from the zip by pointing your Eclipse update manager to the downloaded zip file and following the installation instructions.

Outline

Groovy 1.8.4

Groovy 1.8.4 is now available as an optional install from the update sites.

Compatibility

Groovy-Eclipse 2.6.0 includes Groovy 1.7.10 by default. Groovy 1.8.4 can be optionally installed. This version of Groovy-Eclipse is recommended to be installed on STS 2.8.1 or 2.9.0.M1, Eclipse 3.7.1 or 3.6.2. There are different update sites for Groovy-Eclipse targeting Eclipse 3.6 and 3.7 (see above).

Bug fixes

We have fixed over 70 bugs for this release. See the details on our issue tracker.

Shout outs

We had a very successful Eclipse hackathon in Vancouver, B.C.. We received lots of patches from this event and we hope to do something like this again soon.

  • Some bug and some one fixed it!
  • Some bug and some one fixed it!
  • Some bug and some one fixed it!
  • Some bug and some one fixed it!

And of course, thank you to everyone else who raised bugs on jira and asked questions on the mailing lists.

What's next?

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