The latest version can always be found at Ant's homepage http://jakarta.apache.org/ant/faq.html.

The page you are looking it is generated from this document. If you want to add a new question, please submit a patch against this document to one of Ant's mailing lists, the structure is hoped to be self-explaining.

If you don't know how to create a patch, see the patches section of this page.

We use Anakia to render the HTML version from the original XML file.

The Velocity stylesheets used to process the XML files can be found in the xdocs/stylesheets subdirectory of Ant's CVS repository - the build file docs.xml is used to drive Anakia. This file assumes that you have the jakarta-site2 module checked out from CVS as well, but if you follow the instruction from Anakia's homepage, you should get it to work without that. Just make sure all required jars are in the task's classpath.

Ant is a Java based build tool. In theory it is kind of like "make" without makes wrinkles and with the full portability of pure Java code.

According to Ant's original author James Duncan Davidson, the name is an acronym for "Another Neat Tool".

Later explanations go along the lines of "Ants are doing an extremely good job at building things" or "Ants are very small and can carry a weight a dozen times of their own" - describing what Ant is intended to be.

Initially Ant was part of the Tomcat code base when it was donated to the Apache Software Foundation - it has been created by James Duncan Davidson, who also is the original author of Tomcat. Ant was there to build Tomcat, nothing else.

Soon thereafter several open source Java projects realized that Ant could solve the problems they had with makefiles. Starting with the projects hosted at Jakarta and the old Java Apache project, Ant spread like a virus and now is the build tool of choice for a lot of projects.

In January 2000 Ant was moved to a separate CVS module and was promoted to a project of its own, independent of Tomcat. Ant became Apache Ant.

The first version of Ant that was exposed a lager audience was the one that shipped with Tomcat's 3.1 release on 19 April 2000. This version has later been referenced to as Ant 0.3.1.

The first official release of Ant as a stand alone product was Ant 1.1 released on 19 July 2000. The complete release history:

Ant's distribution contains file names that are longer than 100 characters, which is not supported by the standard tar file format. Several different implementations of tar use different and incompatible ways to work around this restriction.

Ant's <tar> task can create tar archives that use the GNU tar extension, and this has been used when putting together the distribution. If you are using a different version of tar (for example, the one shipping with Solaris), you cannot use it to extract the archive.

The solution is to either install GNU tar, which can be found here or use the zip archive instead (you can extract it using jar xf).

In order to find out which files should be compiled, Ant compares the timestamps of the source files to those of the resulting .class files. Opening all source files to find out which package they belong to would be very inefficient - instead of this, Ant expects you to place your source files in a directory hierarchy that mirrors your package hierarchy and to point Ant to the root of this directory tree with the srcdir attribute.

Say you have <javac srcdir="src" destdir="dest" />. If Ant finds a file src/a/b/C.java it expects it to be in package a.b so that the resulting .class file is going to be dest/a/b/C.class.

If your setup is different, Ant's heuristic won't work and it will recompile classes that are up to date. Ant is not the only tool, that expects a source tree layout like this.

Use properties: ant -D<name>=<value> lets you define values for properties. These can then be used within your build file as any normal property: ${<name>} will put in <value>.

A couple of switches are supported via magic properties:

The short answer is "Use <".

The long answer is, that this probably won't do what you want anyway, see the next section.

Say you want to redirect the standard input stream of the cat command to read from a file, something like

and try to translate it into

This is probably happening because by default, Ant excludes SourceSafe control files (vssver.scc) and other files from FileSets.

Here's what you probably did:

There are actually several answers to this question.

If you have only one set and one unset property to test, you can put both an if and an unless attribute into the target. The target will act as if they are "anded" together.

If you are using a version of Ant 1.3 or earlier, the way to work with all other cases is to chain targets together to determine the specific state you wish to test for.

To see how this works, assume you have three properties, prop1, prop2, and prop3. You want to test that prop1 and prop2 are set, but that prop3 is not. If the condition holds true you want to echo "yes".

Here is the implementation in Ant 1.3 and earlier:

Note that <antcall> tasks do not pass property changes back up to the environment they were called from.

Starting with Ant 1.4, you can use the <condition> task.

This version takes advantage of two things:

• If a property a has not been set, ${a} will evaluate to ${a}.
• To get a literal $ in Ant, you have to escape it with another $ - this will also break the special treatment of the sequence ${.

This is neither readable, nor easy to understand, therefore post-1.4.1 Ant introduces the <isset> element to the <condition> task.

Here is the previous example done using <isset>:

The last option is to use a scripting language to set the properties. This can be particularly handy when you need much better control than the simple conditions shown here, but of course comes with the overhead of adding JAR files to support the language, to say nothing of the added maintenance in requiring two languages to implement a single system.

The list of dependencies is generated by Ant before any of the targets are run. This allows dependent targets such as an init target to set properties that can control the execution of the targets higher in the dependency graph. This is a good thing.

When your dependencies actually break down the higher level task into several simpler steps, though, this behaviour becomes counterintuitive. There are a couple of solutions available:

1. Put the same condition on each of the dependent targets.
2. Execute the steps using <antcall> instead of specifying them inside the depends attribute.

The order of the <include> and <exclude> tags within a fileset is ignored when the fileset is created. Instead, all of the <include> elements are processed together, followed by all of the <exclude> elements. This means that the <exclude> elements only apply to the file list produced by the <include> elements.

To get the files you want, focus on just the <include> patterns that would be necessary to get them. If you need to trim the list that the includes would produce, use excludes.

See the section on IDE integration on our external tools page.

Ant adds a "banner" with the name of the current task in front of all messages - and there are no built-in regular expressions in your Editor that would account for this.

You can disable this banner by invoking Ant with the -emacs switch. Alternatively you can add the following snippet to your .emacs to make Emacs understand Ant's output.

Yet another alternative that preserves most of Ant's formatting is to pipe Ant's output through the following Perl script by Dirk-Willem van Gulik:

An incomplete DTD can be created by the <antstructure> task - but this one has a few problems:

• It doesn't know about required attributes. Only manual tweaking of this file can help here.
• It is not complete - if you add new tasks via <taskdef> it won't know about it. See this page by Michel Casabianca for a solution to this problem. Note that the DTD you can download at this page is based on Ant 0.3.1.
• It may even be an invalid DTD. As Ant allows tasks writers to define arbitrary elements, name collisions will happen quite frequently - if your version of Ant contains the optional <test> and <junit> tasks, there are two XML elements named test (the task and the nested child element of <junit>) with different attribute lists. This problem cannot be solved, DTDs don't give a syntax rich enough to support this.

You can use XML's way of including external files and let the parser do the job for Ant:

will literally include the contents of common.xml where you've placed the &common; entity.

In combination with a DTD, this would look like this:

If you are using a nightly-build of Ant 1.5 after 2001-12-14, you can use the built-in MailLogger.

See the Listener & Logger documentation for details on the properties required.

For older versions of Ant you can use a custom BuildListener, that sends out an email in the buildFinished() method. Will Glozer <will.glozer@jda.com> has written such a listener based on JavaMail, the source is

With a monitor.properties like this

You can get at a hashtable with all the properties that Ant has been using through the BuildEvent parameter. For example:

This is more accurate than just reading the same property files that your project does, since it will give the correct results for properties that are specified on the command line when running Ant.

The antRun script in ANT_HOME/bin has DOS instead of Unix line endings, you must remove the carriage return characters from this file. This can be done by using Ant's <fixcrlf> task or something like:

There is a bug in the Solaris reference implementation of the JDK, see http://developer.java.sun.com/developer/bugParade/bugs/4230399.html. This also appears to be true under Linux, moving the JDK to the front of the PATH fixes the problem.