Gant is a build tool for scripting Ant tasks using Groovy instead of XML to specify the build logic. A Gant build specification is a Groovy script and so can bring all the power of Groovy to bear directly, something not possible with Ant scripts. Whilst it might be seen as a competitor to Ant, Gant uses Ant tasks for many of the actions, so Gant is really an alternative way of doing builds using Ant, but using a programming language rather than XML to specify the build rules.
Here is an example Gant script:
In this script there are two targets, stuff and otherStuff -- the default target for this build is designated as stuff and is the target run when Gant is executed from the command line with no target as parameter.
Targets are closures so they can be called as functions, in which case they are executed as you expect, or they can be dependencies to other targets by being parameters to the depends function, in which case they are executed if an only if they have not been executed already in this run. (There is a page with some more information on Targets.)
You may be wondering about the stuff at the beginning of the script. Gant has two ways of using pre-built sub-scripts, either textual inclusion of another Gant script or the inclusion of a pre-compiled class. The example here shows the latter -- the class gant.targets.Clean is a class that provides simple clean capabilities.
The default name for the Gant script is build.gant, in the same way that the default for an Ant build script in build.xml.
Gant provides a way of finding what the documented targets are:
The messages on this output are exactly the strings associated with the target name in the introduction to the target.
Gant can build and install itself to an existing Groovy installation and is being used for various build tasks including building Groovy and Java programs, static websites, LaTeX documents. The ability to have arbitrary Groovy methods within the build scripts makes a Gant build script so much easier to work with that the mix of XML and Groovy scripts that using Ant necessitates. But then maybe this is an issue of individual perception. But then Gant is not about replacing Ant, it is about having a different way of working with the tasks and infrastructure that Ant provides.
Some pages providing more details:
Gant is currently at version 1.2.0, it requires Groovy version 1.0 or later. The following downloads are available:
There is a file README_Install.txt in the distribution.
The jar and pom have been uploaded to the Codehaus Maven repository, the groupId is org.codehaus.gant, the artifactId is gant and the version is 1.2.0.
Users who are using Groovy from Subversion Trunk or a 1.6 beta may want to use:
Debian users (almost certainly also Ubuntu users) can install Gant using the usual package management system. Lenny (testing) has Gant 1.1.1 http://packages.debian.org/lenny/gant as does Sid (unstable) http://packages.debian.org/sid/gant, both are dependent on Groovy which in both distributions is 1.5.4.
An old Ubuntu/Debian package of Gant 1.0.2 for Groovy 1.5 is available: Deb
Ealier distributions are available at http://dist.codehaus.org/gant/distributions as are snapshots of the next release, if available.
If you would prefer to work with the version in the Groovy Subversion repository, you can get a copy usaing Subversion by:
Bazaar, Git and SVK have mechanisms for mirroring a Subversion repository, and are known to work well. In particular, there is a maintained Bazaar branch at:
Gant is the main tool for working with the Gant checkout, but (obviously the first time you want to install Gant from a checkout there is no Gant to build and install Gant. To cover this situation there is an Ant build script for bootstrapping.
If you give it a go and have some feedback, do let me know either on the Gant User mailing list or perhaps the Groovy User mailing list, or by direct email to me email@example.com
If you have any issues with Gant then please add a JIRA issue into the Gant JIRA at Codehaus. The URL is http://jira.codehaus.org/secure/CreateIssue!default.jspa