In the final release of Groovy-Eclipse 2.1.1, just 6 weeks after our previous release of 2.1.0, there are many exciting new features to look forward to.
You can use the following update site to install this release. To install, copy and paste this link into your Eclipse update manager:
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 provided by the update manager.
- Inferencing inside of closures
- Inferencing of statically imported fields and methods
- Content assist for Constructors
- Improved semantic highlighting
- Organize imports improvements
- Create Groovy Script
- Outline view for binary Groovy types
- Bookmarks and Tasks
- Groovy Event Console
- Bug fixes
- What's next?
Inferencing inside of closures
Type inferencing and content assist inside of closures now uses the type of calling method as the type of
this. For example, the following code snippet with use
User as the type of
this inside the closure:
Similarly, content assist will work as expected:
For more information, see GRECLIPSE-916.
The quickfixes can be invoked like any other standard Java quickfix, either by clicking on the light bulb in the gutter:
By hovering over the exception:
By using the keyboard shortcut (CTRL-1 or CMD-1 on macs), or through the problems view:
The convert to Groovy file quick fix is available whenever there is an error in your Java code that looks like Groovy syntax (for example, a missing semi-colon):
Inferencing of statically imported fields and methods
Statically imported fields and methods are now available from content assist and in the inferencing engine.
See GRECLIPSE-698 for more information.
Content assist for Constructors
Content assist now includes appropriate constructors when invoked in front of a
Improved semantic highlighting
Semantic highlighting now highlights field references, static references, and deprecated references as shown in the example below:
Organize imports improvements
Organize imports in Groovy scripts now respects the settings in
Preferences -> Java -> Code Style -> Organize Imports. Imports are sorted appropriately and grouped according to preferences. Also, semi-colons are now automatically removed.
For example, the following simple script is originally:
And becomes this after organize imports is invoked:
Create Groovy Script
The New Groovy Class wizard now has an option to create a Groovy script instead of a standard class. To create a script, select the "Create Script" check box in the New Groovy class wizard as shown here:
Outline view for binary Groovy types
When binary Groovy types are shown in the outline view and the package explorer all synthetic methods and fields are filtered from the view. See GRECLIPSE-865.
Bookmarks and Tasks
It is now possible to add a bookmark or a task in a Groovy file by right-clicking on the editor ruler and selecting '
Add Bookmark...' or '
Add Task...' as shown here:
Groovy Event Console
Groovy-Eclipse now ships with a Groovy event console that prints out information of the internal workings of Groovy-Eclipse. You can access the console from the console view and clicking on the Open Console button:
Most of this information is for debugging of Groovy-Eclipse itself and will be used in the future to help diagnose problems on users' machines.
Groovy-Eclipse 2.1.1.RC1 includes Groovy 1.7.5 and is installable on Eclipse 3.6.0 and 3.6.1. There are no plans to release a 3.5 version of this release.
Over 65 issues have been addressed for this release.
The Groovy-Eclipse team would like to thank Nieraj Singh for his excellent work on the new Groovy-Eclipse Quick Fix feature. We'd also like to thank the community for continuing to provide feedback, raising issues, and for telling us what you need. Keep it up! You are what keeps this project alive.
We are planning the 2.1.2 release for March 2011. 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.