Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current ·  View Page History

Groovy is an agile dynamic language for the Java 2 Platform that has many of the features that people like so much in languages like Python, Ruby and Smalltalk, making them available to Java developers using a Java-like syntax.

Groovy is designed to help you get things done on the Java 2 Platform in a quick, concise and fun way — Groovy brings the power of a scripting language directly into the Java 2 Platform. For example:

  • Shell scripting using Groovy allows the full power of the Java Platform to be brought to bear to the task at hand.
  • Groovy can be used (and indeed is already being used) as a replacement for Java for small and medium sized applications to execute on the Java 2 Platform.
  • Groovy can be used as an embedded language for dynamic business rules or extension points utilizing the agility of Groovy and saving the cost of redeploying applications for each change of rule (especially when the rules are stored in a database).
  • Groovy makes writing test cases for unit tests very easy.

As well as being a powerful language for scripting Java objects, Groovy can be used as an alternative compiler to javac to generate standard Java bytecode to be used by any Java project.

Features

News

Dear all,

I'm pleased to announce the release of Groovy 2.1.5.

Groovy 2.1.5 is a bug fix release of the Groovy 2.1 branch. In particular, it fixes a problem we've encountered with Groovy 2.1.4 where the extension module descriptors were not found in the "all" JAR, which meant that the usual nice GDK methods extensions for XML and other modules were not found by Groovy.

You can download Groovy 2.1.5 in the download area and have a look at the JIRA release notes.

Thanks to all who contributed to this release!

Keep on groovy'ing!

Groovy 2.1.4 released

The Groovy development team is pleased to announce the release of Groovy 2.1.4.

Groovy 2.1.4 is essentially a bug fix release of our 2.1 branch, and you can dive into the details in our JIRA release notes.

You can get the distribution in our download area.

Thanks a lot to all those who contributed to this release, and we're looking forward to hearing your feedback!

The Groovy team is always looking at ways to further improve and encourage the collaboration and contributions from the community.
Today, the we are looking for a sponsor for a dedicated server that would host our new Continuous Integration server. If you or your company is interested in helping Groovy by contributing hardware and/or hosting, please contact us.
On behalf of the Groovy team, thanks in advance for your help and support!
We're looking forward to hearing from you.
Heads up on a joint bug-fix release, with Groovy 2.0.8 and 2.1.3.
We released the 2.0.8 bug fix in particular for Grails which was affected by a couple issues but that hadn't planned on migrating just yet to the 2.1.x line.
If you want to learn more about the issues closed, please have a look at the JIRA release notes for Groovy 2.0.8 and Groovy 2.1.3
Head down to the Download section to download our the latest releases.
Thanks for all your contributions, and keep on groovy'ing!

The Groovy development team is happy to announce the joint releases of Groovy 1.8.9, 2.0.7, and 2.1.1!

Those three releases are essentially bug fix releases.
You can have a look at the JIRA issues we tackled here:
Head over to the Groovy distribution area to download the Groovy distributions and documentation.
Some further notes about our current releases and branches:
Groovy 1.8.9 is the last planned update for the 1.8 versions of Groovy unless critical bugs arise. 
When resolving bug requests we may not automatically apply them to the 1.8 versions of Groovy as we are trying to focus on later releases when we can and backporting some of the fixes can be a little tricky. 
However, if you have a critical bug and are unable to upgrade, please indicate that in the relevant jira issue and we will try to take that into account when resolving issues. 
Of course patches/pull requests against the 1_8_X branch are also welcome! :-)
Releasing Groovy 2.0.7 wasn't strictly necessary as upgrading to Groovy 2.1.1 is straightforward but we wanted to make a formal last release for the 2.0.x branch. 
And going forward, bug fixes will be targeted at both 2.1.x and 2.2 lines, and only 2.2 will get any new features that may come, but we don't anticipate that 2.0.x will get further fixes as the 2.1.x line supersedes that branch.

Thanks a lot to all those who contributed to this release, and we're looking forward to hearing about your feedback!

Read more News on the Groovy Blog

Getting started

Probably the best way to get started on Groovy is to [install a binary distribution|Download} and play with it.

Or try reading the [user guide|Language+Guide} or browsing some of the links on the left of this page.

Current build status

The Groovy project uses DamageControl as a Continuous Integration system to make Groovy build automatically. The little coloured bubble on the left show the status of the last automatic build: if it's green, the build was successful, if it's red, the build failed. And if it is pulsating, it means there's a new build currently in the works.

Labels
  • None