The Groovy development team and SpringSource are happy to announce the joint release of Groovy 1.6.4 and a preview of Groovy 1.7.
- Groovy 1.6.4 is the latest release of our 1.6 stable branch, and contains mainly bug fixes and minor enhancements.
- Groovy 1.7-beta-1 is the first preview of the upcoming Groovy 1.7 and provides several new features.
Be sure to have a look at the new features coming into Groovy 1.7:
- anonymous inner classes / nested classes
- improved annotations available in more places beyond Java 5 (on imports, packages and on variable declarations)
- a new shorcut notation for the @Grab annotation
- power asserts to make assertion failures way more readable and useful, coming right from Spock's feature set
- an AST Viewer in the Groovy Swing Console
- an AST Builder to ease the creation and authoring of AST transformations
- a rewrite of the GroovyScriptEngine (also used in Groovlets, Gaelyk, and the Groovy Web Console on Google App Engine) with better dependency management and faster compilation
- several various Swing enhancements thanks to our Griffon team
- the Groovy Swing Console remembering position and font size preferences
- and enhancements in the Sql class support with the addition of transaction and batch capabilities
Let me also remind you yesterday's very important release of the first preview version of the new Eclipse plugin for Groovy, contributed by SpringSource's Eclipse team. An interview of the developer team will follow soon on GroovyZone.
You can download 1.6.4 and 1.7-beta-1 in the download area.
Have a look at the JIRA issues closed for both versions.
Thanks a lot to all involved, users, contributors, developers, make sure to enjoy these new important releases and enjoy your vacations if you take some this summer!
The Groovy development team.
Dear Groovy community,
I'm happy to announce the release of Spock Framework 0.2! Some highlights of this release are:
- Example project with Ant, Gradle, and Maven build - download, unzip, run!
- Smart stack traces point directly to the cause of the problem
- Improved IDEA integration (for example, it is now possible to run a single test method, or to re-run all failed test methods)
- Enhanced visualization of data-driven tests
- Void methods can now be safely called from 'expect' and 'then' blocks
- More accurate error messages for invalid specifications
How can you get involved? Spread the word, give Spock a try, provide feedback, or submit a patch!
Example project: http://spock.googlecode.com/files/spock-example-0.2.zip (see README for instructions)
Discussion forum: http://forum.spockframework.org
As usual, Spock 0.2 is also available from Maven Central (http://repo1.maven.org).
Thanks to Hamlet D'Arcy, Neal Ford, Paul King, Dirk Koenig, Guillaume Laforge, and everyone else who helped spread the word about Spock.
Special thanks to Rainer Kelz for pointing out that Spock is, almost by definition, Enterprise ready.
GParallelizer, the opensource concurrency and actor library for Groovy, has reached its 0.8 release. Besides further maturing the actor support and the collection concurrency, you can now find an inspiring Dataflow Concurrency DSL bundled with GParallelizer. Check out the details on Dataflow Concurrency on the project wiki.
To list a few of the new features, here's the top 5 items from the release notes:
- Added DataFlow concurrency support
- Enabled asynchronous collection processing through meta-class enhancements
- Added sendAndWait() methods to actors to block the caller until a reply arrives
- Ability to join actors to await their termination
- Added special-purpose actors, the DynamicDispatchActor and the ReactiveActor, to allow for an alternative message handling syntaxes
Check out GParallelizer today and don't forget to experiment with all the samples.
To get a feel for what actors can do for you, have a look at the sample actor solutions to several common concurrency issues, like The Dining Philosophers or The Sleeping Barber.
Thank everyone for the feedback I've received. Since it is the comments and suggestions I hear from the community that drives my development further, please, keep on commenting.