Getting The Tools

If you don't have the tools installed already that Glean uses, you can get them a couple of different ways. The tools page has a list of download links that get you to that tool's site, and you can follow their instructions for download and setup.

There is also an Ant script in the Glean installation that is able to download about a dozen of the tools from public Maven repositories. It requires the Maven Ant tasks be installed, which is just one manual download, compared with a dozen. The script will also generate a properties file for Glean telling it where each of these tools is installed.

Download the Maven Ant tasks and install them where Ant knows about them (instructions are on the Maven Ant tasks page)
Run the Glean Ant script. By default, the tools will go to a directory under ${user.home}/temp, and a toolhome.properties.local file will be created in the same place.
```
ant download-tools
```
You can specify the root of the tools area as well as the location of the generated properties file with properties on the command line.
```
ant download-tools \
    -Dtools.base=/path/to/tool/base/dir \
    -Dtoolhome.props=/path/to/toolhome.properties.local
```

Defining Tool Homes

Glean uses a pair of properties files to tell it where each of the tools it uses can be found.

The file toolhome.properties comes with Glean, and defines some defaults that may or may not correspond to your particular installation.
The file toolhome.properties.local, if it exists, is read before the default file and is meant to let you define where your particular tools are if they differ from the default locations.

These files are simple properties files, with the convention that the property name is

(Glean tool name)home.properties

Glean uses this convention to set up the tasks and paths needed for that tool to run.