I'm pleased to announce the second release candidate for Groovy 1.0.
Groovy 1.0 RC-2 is a bug-fix release. We focused our time on correcting bugs encountered in RC-1 and older bugs related to bytecode issues. Like in the previous releases, some better compilation error messages have been improved as well.
We would like you to try out this Release Candidate and to report as soon as possible all the potential problems you could encounter. The final release is now really imminent, and you should expect it before new year's eve, or in the very beginning of January. So please help us test this release on your own projects, so that we can deliver the best possible final release!
You can find the latest groovy-all jar here:
http://dist.groovy.codehaus.org/jars/groovy-all-1.0-RC-02.jar
And the distribution here:
http://dist.groovy.codehaus.org/distributions/groovy-1.0-RC-02.zip
This RC-2 release is the gift of the Groovy team to its users, and we're wishing you all a Groovy Christmas and a happy New Year with your beloved ones.
--
Guillaume Laforge
Groovy Project Manager
Hiall,
I'm happy to announce that the Groovy in Action book is
now available in the ebook version under
http://groovy.canoo.com/gina.
The softcover print version will be available on the first
week of January. At that time, booksellers will also ship
the pre-ordered copies.
enjoy reading
Dierk
InfoQ, the news site tracking innovation and change in the enterprise community, is covering the release of Groovy RC-1. They also feature an in-depth interview of Guillaume Laforge, the Groovy Project Manager and JSR-241 Spec Lead.
This is with great pleasure that I'm announcing the release of the first release candidate of Groovy.
Groovy RC-1 is a very important milestone in the life of the project.
It also means 1.0 will be released very shortly thereafter.
The plan is to release the final version before the end of the month.
This release contains a re-implemented and reworked Meta-Object Protocol, which is the core of Groovy's runtime system which decides how the dispatch of method calls, property and attribute access works.
This new MOP brings more flexibility and a finer-grained control of those mechanisms.
But unless you need tweaking that advanced dispatching logic, those changes won't affect you.
Groovy RC-1 contains a lot of bug fixes and improvements -- about a hundred have been worked out in this release.
Among the interesting improvements, you'll note that coercion mechanisms are improved and now customizable for your own POGOs through the asType(Class) method.
You can even coerce Maps to interfaces, as well as Closures to single-method interfaces.
The 'in' keyword now becomes a fully supported boolean operator, not only in the for loop.
Last but not least in the dynamicity of the language, you can decide which method to call with GStrings, like in: foo."$methdName"(*args).
So far, the old closure notation with the vertical pipe was still allowed, and the @Property syntax was silently ignored in the latest release.
Now that the transition period is over, in RC-1 both are definitely illegal.
I hope you will all have already updated your codebase.
For a mode detailed list of the bug fixes and improvements, please refer to JIRA.
You can download Groovy RC-1 at the usual place .
Thanks goes to all the team for its efforts, and particularly Jochen Theodorou for his hard work.
Big bravos to John Wilson for the XML support and the MOP, Guillaume Alléon for patches and Groovy SOAP, Dierk Koenig and it co-authors for the great Groovy in Action book, and the Eclipse plugin team as well.
And also thanks to the brand new commiters who are bringing some fresh blood to the team, for instance Paul King who helped us improve some important error messages!
The list is too long to name everybody!
Happy Groovying!
PS: InfoQ is covering the release and also features an interview with the Groovy Project Manager.
--
Guillaume Laforge
Groovy Project Manager