Eclipse version compatability
Eclipse 3.1 : not working
Eclipse 3.2 : working
Addition one: LANG metadata keyword
First, there is a new metadata keyword called LANG, which as is implied, determines what scripting language you wish to use. Here is an example of an Eclipse Monkey base example ported to Groovy:
Notice the LANG tag, that is all there is to that.
Addition two: Outline view
Secondly, the outline view is populated showing the binding variable names and types with their publicly available methods and fields. This can be useful since the DOMs are loaded on your eclipse ide as plugins and not in your workspace view. Even if you were to load in the DOMs into your workspace, there is still a great deal of switching that must be done.
Addition three: Groovy SWT and Launch Manager DOMs
Thirdly, there are new DOMs that are located on the update site that include direct access to a console for output, enable you to script your launch configurations together and a wrapper for the Groovy SWT project as a DOM.
Here is an example of a script, copied from the examples given in Groovy-SWT, ported into Groovy Monkey.
Here is an example of a script that uses the Launch Configuration Manager DOM along with the JFace/SWT DOM and the Console output DOM. It prints out the list of all your available launch configurations and allows you to select which ones you wish to string together.