Message-ID: <173376610.19342.1406747792314.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_19341_1043661558.1406747792314" ------=_Part_19341_1043661558.1406747792314 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
At the start of May 2009 we announced we were working on a new approach= to joint compilation for mixed Java/Groovy projects in Eclipse. We are ple= ased to now announce the final release of Groovy-Eclipse v2.0.0, based on t= hat new technology. During the months of development we have rebased (and a= lmost entirely rewritten) version 1 of the Groovy-Eclipse plugin, with the = goal of offering first class Groovy support in the Eclipse IDE, comparable = to the experience Java developers have in Eclipse. The driving themes for v= ersion 2.0.0 have always been to optimize around the common developer actio= ns of editing, building, running and testing code:=20
More information on all these features can be found in the New and Notew= orthy for the milestones and release candidates leading up to this release:==20
Some of the features we will be working on in the near term:=20
You can find more details on the Groo= vy-Eclipse Roadmap, where you can comment on proposed features and see = our release schedule.=20
We appreciate all the community support and feedback we have had through= the version 2.0.0 development cycle. If you wish to join the discussion ab= out Groovy-Eclipse then please sign up for the mailing list. For any issues you have (o= r enhancements you'd like to see), please raise them in our issue tracker.=20
Groovy-Eclipse 1.5.7 was the last public release and since then over 380= bugs have been fixed in the run-up to version 2:com.atlassian.conflue= nce.macro.MacroExecutionException: The URL filter is not available to you, = perhaps it has been deleted or had its permissions changed=20
If the above doesn't show for you, go directly to the jira issue tracker.