After half a year of unremittingly working on Groovy-Eclipse and an almost complete rewrite of the code base, we are announcing the final release of Groovy-Eclipse 2.0.0. We have rebased the Eclipse builder on a joint Java-Groovy compiler built on top of Eclipse's Java Development Tools. What this means is that there is no need for a stubs compiler, there can be true cross-language, inter- and intra-project dependencies, and incremental compilation is available just like in any standard Java project. On top of that the Groovy-Eclipse plugin comes with tight integration with Java, advanced and extensible content assist, debug support, and an inferencing engine that can determine the type of any expression in the editor.
All of these features are described in detail in the New and Noteworthy pages for our previous milestone releases, see Groovy-Eclipse 2.0.0M1 New and Noteworthy, Groovy-Eclipse 2.0.0M2 New and Noteworthy, and Groovy-Eclipse 2.0.0RC1 New and Noteworthy.
Planning for 2.1.0 and beyond
This is just the beginning and we have big plans for the future of Groovy-Eclipse.
Issues fixed since Groovy-Eclipse 1.5.7
Groovy-Eclipse 1.5.7 was the last public release and it is with great pleasure that I can see we have fixed over 380 bugs since then (and our bug database has 620 bugs logged in it total, so that's well over half).com.atlassian.confluence.macro.MacroExecutionException: The URL filter is not available to you, perhaps it has been deleted or had its permissions changed
If the above doesn't show for you, go directly to the jira issue tracker.
Thank you to the community for diligently trying out new releases, raising bugs, suggesting fixes, and discussing features. If you want to participate in the discussion, join the mailing list and raise bugs in our issue tracker.