The Gant master repository is the Git repository held at Codehaus:
Development work can therefore be undertaken by cloning the repository and hacking away.
git clone git://git.codehaus.org/gant.git Gant
git clone ssh://firstname.lastname@example.org/gant.git Gant
Committer access requires the committer to have public SSH keys uploaded to Codehaus.
People using anonymous access should send merge requests to Russel Winder via the Gant Developer mailing list.
Development used to be undertaken using Bazaar, and indeed that can still be the case even though Codehaus does not support Bazaar – bzr-git allows Bazaar to work with a Git repository. Launchpad is used to store Bazaar series maintenance and feature branches. To get a Bazaar branch direct from the Git repository:
bzr branch git://git.codehaus.org/gant.git Gant
will create a Bazaar branch of the master branch, aka trunk.
An alternative is to branch from the trunk mirror Bazaar branch held on Launchpad. To get a branch of that branch:
bzr branch lp:gant Gant
This should (under normal circumstances) be identical to the branch held in the Codehaus Git repository. Where there are conflicts, the Git repository on Russel Winder's server (http://www.russel.org.uk/Git/Gant.git) is the final arbiter:
git clone http://www.russel.org.uk/Git/Gant.git Gant
Up to and including Gant 1.8.1, Gant had been used as the build tool for working with the Gant source, but (obviously ) the first time you wanted to install Gant there may not have be a Gant installation to build and install Gant. To cover this situation there was an Ant build script for bootstrapping. From Gant version 1.9.0 onwards Gradle is the principle build tool for managing Gant development. An instance of the Gradle Wrapper is now included in the Gant source tree.
Further details in README_Install.txt in the Gant source tree.