Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Groovy-Eclipse now allows you to search for references to generated getters, setters and properties. For example, searching for references to a Groovy property (such as age in this example) will find all references to getAge and setAge in both Java and Groovy files:


For more information on this feature, see issues GRECLIPSE-1204, GRECLIPSE-1010, and [GRECLIPSE-1205|

Better default parameter support


For more information on this feature, see issues GRECLIPSE-1255, and GRECLIPSE-1233.

Better extract local variable refactoring

Extract local variable is now more precise as to where the variable is extracted to. Now, the variable is placed in the statement immediately preceding the variables variable's first use. See this example, where '' is extracted to a variable and placed inside the enclosing closure.

See issue GRECLIPSE-907.

Parser Recovery


It is now possible to selectively suppress DGMs from cluttering up content assist. There is a new Preferences -> Groovy -> Content Assist preferences page:


As expected, when in the editor, entries that have been suppressed no longer appear in content assist. In this case, each has been filtersfiltered, but eachWithIndex has not:


The Groovy-Eclipse classpath container now includes the ivy, jline, and bsf jars by default. Even thought these libraries are not typically used directly in user code, including them on the classpath will help with searching for binary references. See GRECLIPSE-1211.

Maven integration

There is now better ordering on the Java classpath of Groovy source folders when importing maven projects that user Groovy into Eclipse and STS. See GRECLIPSE-1222,


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).


Shout outs

We had a successful Eclipse hackathon this November in Vancouver, B.C. and we received a number of quality patches from external contributors:

Thanks for your work. And of course, thank you to everyone else who contributed in other ways by raising bugs on jira or asking questions on the mailing lists.