Groovy-Eclipse 2.0.0RC1 New and Noteworthy

Riding high on the back of the Groovy 1.7 release, the Groovy-Eclipse is pleased to announce its own 2.0.0RC1 release. Over 50 issues have been addressed for this release and we consider this release high quality enough to be considered for release in early January, unless blocking bugs are found.

In this release, we have focused on polishing and refining existing features, but there are some new features introduced as well.

Better @Grab support

Andy can you add something here?

Launching Groovy scripts

Launching groovy scripts is now easier and more robust. We have addressed some key bugs in this area: GRECLIPSE-555, GRECLIPSE-560, GRECLIPSE-478.

There is also an option to set the default working directory for the script launcher:

img

On the Groovy Preferences page, you can toggle between the project root, the workspace root, and the script location.

Additionally, the Run as Groovy Application launch configuration has been removed since it is a complete duplicate of the Java launch configuration. All compiled groovy scripts can be launched as a Java application through its generated main method.

Inferencing improvements

We are continuing to refine the inferencing engine (link?). Some of the notable improvements is support for navigation on the super, and this keywords. Also, content assist will show all the proper method and property completions when the class literal is accessed, e.g.:

img (show Foo.class. content assist)

img (show Foo. content assist)

Better parser recovery

Andy can you add something here?

Better AST transform support

Andy can you add something here?

Jars from .groovy/lib directory added to classpath

All jars in your <user.home>/.groovy/lib directory are added to your classpath as part of the Groovy support classpath container. After a change to the groovy lib directory, you can refresh the workspace's Groovy support classpath container by going to the Groovy Preferences page:

img

Groovy-aware file copy/rename

Groovy-aware file copy, rename, and paste are working. In the package explorer, you can select a groovy compilation unit and type CTRL-c and CTRL-v (or CMD-c and CMD-v on Mac). The compilation unit will be appropriately copied.

Furthermore, you can rename a class inside of a Groovy compilation unit:

Select a class reference, right click, and choose Refactor -> Rename:

img (show refactoring menu on a class)

In the dialog, there are two options:

img (show rename reactoring dialog)

The first will rename the file along with the refactoring, and the second will keep the file name the same and only rename the class.

Navigate to super class

Clicking on the override arrow indicator in the gutter will navigate the caret to the super class's implementation of a method:

img

JavaDoc viewing

Hovering on a Groovy method field or class will bring up the JavaDoc/GroovyDoc comment for that declaration. For more information, see the Groovy eclipse and javadoc hovers blog post.

Generated getter/setter navigation and JavaDocs

img show JavaDoc of hovering over generated getter.

Basic content assist options

There are now some basic options to control how content assist proposals are entered into the Groovy editor. You can control whether or not parentheses are used for entering method proposals. And you can also control whether closures arguments are entered with an empty closure { } or as a regular parameter.

img show the preferences page.

Issues fixed

If the above doesn't show for you, go directly to the jira issue tracker