|Original author(s)||James Duncan Davidson|
|Developer(s)||Apache Software Foundation|
|Initial release||19 July 2000|
1.10.5 / July 13, 2018
|License||Apache License 2.0|
Apache Ant is a software tool for automating software build processes, which originated from the Apache Tomcat project in early 2000. It was a replacement for the Make build tool of Unix, and was created due to a number of problems with Unix's make. It is similar to Make but is implemented using the Java language, requires the Java platform, and is best suited to building Java projects.
The most immediately noticeable difference between Ant and Make is that Ant uses XML to describe the code build process and its dependencies, whereas Make uses the Makefile format.
By default, the XML file is named
Ant ("Another Neat Tool") was conceived by James Duncan Davidson while preparing Sun Microsystems's reference JSP and Servlet engine, later Apache Tomcat, for release as open-source. A proprietary version of Make was used to build it on the Solaris platform, but in the open-source world, there was no way of controlling which platform was used to build Tomcat; so Ant was created as a simple platform-independent tool to build Tomcat from directives in an XML "build file". Ant (version 1.1) was officially released as a stand-alone product on July 19, 2000.
Several proposals for an Ant version 2 have been made, such as AntEater by James Duncan Davidson, Myrmidon by Peter Donald and Mutant by Conor MacNeill, none of which were able to find large acceptance with the developer community.
At one time (2002), Ant was the build tool used by most Java development projects. For example, most open source Java developers included
build.xml files with their distribution. Because Ant made it trivial to integrate JUnit tests with the build process, Ant made it easy for willing developers to adopt test-driven development, and even extreme programming.
WOProject-Ant is just one of many examples of a task extension written for Ant. These extensions are installed by copying their
.jar files into ant's
lib directory. Once this is done, these task extensions can be invoked directly in the typical
build.xml file. The WOProject extensions allow WebObjects developers to use ant in building their frameworks and apps, instead of using Apple's Xcode suite.
Below is listed a sample
build.xml file for a simple Java "Hello, world" application. It defines four targets -
jar , each of which has an associated description. The
jar target lists the
compile target as a dependency. This tells Ant that before it can start the
jar target it must first complete the
<?xml version="1.0"?> <project name="Hello" default="compile"> <target name="clean" description="remove intermediate files"> <delete dir="classes"/> </target> <target name="clobber" depends="clean" description="remove all artifact files"> <delete file="hello.jar"/> </target> <target name="compile" description="compile the Java source code to class files"> <mkdir dir="classes"/> <javac srcdir="." destdir="classes"/> </target> <target name="jar" depends="compile" description="create a Jar file for the application"> <jar destfile="hello.jar"> <fileset dir="classes" includes="**/*.class"/> <manifest> <attribute name="Main-Class" value="HelloProgram"/> </manifest> </jar> </target> </project>
Within each target are the actions that Ant must take to build that target; these are performed using built-in tasks. For example, to build the
compile target Ant must first create a directory called
classes (which Ant will do only if it does not already exist) and then invoke the Java compiler. Therefore, the tasks used are
javac. These perform a similar task to the command-line utilities of the same name.
Another task used in this example is named
This Ant task has the same name as the common Java command-line utility, JAR, but is really a call to the Ant program's built-in JAR/ZIP file support. This detail is not relevant to most end users, who just get the JAR they wanted, with the files they asked for.
Many Ant tasks delegate their work to external programs, either native or Java. They use Ant's own
<java> tasks to set up the command lines, and handle all the details of mapping from information in the build file to the program's arguments and interpreting the return value. Users can see which tasks do this (e.g.
<rpm>), by trying to execute the task on a system without the underlying program on the path, or without a full Java Development Kit (JDK) installed.
One of the primary aims of Ant was to solve Make's portability problems. The first portability issue in a Makefile is that the actions required to create a target are specified as shell commands which are specific to the platform on which Make runs. Different platforms require different shell commands. Ant solves this problem by providing a large amount of built-in functionality that is designed to behave the same on all platforms. For example, in the sample
build.xml file above, the clean target deletes the
classes directory and everything in it. In a Makefile this would typically be done with the command:
rm -rf classes/
rmdir /S /Q classes
In an Ant build file the same goal would be accomplished using a built-in command:
A second portability issue is a result of the fact that the symbol used to delimit elements of file system directory path components differs from one platform to another. Unix uses a forward slash (/) to delimit components whereas Windows uses a backslash (\). Ant build files let authors choose their favorite convention: forward slash or backslash for directories; semicolon or colon for path separators. It converts each to the symbol appropriate to the platform on which it executes.
This article's Criticism or Controversy section may compromise the article's neutral point of view of the subject. (September 2011)
This section possibly contains original research. (September 2011) (Learn how and when to remove this template message)
- Ant build files, which are written in XML, can be complex and verbose, as they are hierarchical, partly ordered, and pervasively cross-linked. This complexity can be a barrier to learning. The build files of large or complex projects can become unmanageably large. Good design and modularization of build files can improve readability but not necessarily reduce size. Other build tools, such as Gradle or Maven, use more concise scripts at the expense of generality and flexibility.
- Many of the older tasks—the core ones that are used every day, such as
<java>—use default values for options that are not consistent with more recent versions of the tasks. Changing those defaults would break existing Ant scripts.
- When expanding properties in a string or text element, undefined properties are not raised as an error, but left as an unexpanded reference (e.g.
- Ant has limited fault handling rules.
- Lazy property evaluation is not supported. For instance, when working within an Antcontrib
<for>loop, a property cannot be re-evaluated for a sub-value which may be part of the iteration. (Some third-party extensions facilitate a workaround; AntXtras flow-control tasksets do provide for cursor redefinition for loops.)
- In makefiles, any rule to create one file type from another can be written inline within the makefile. For example, one may transform a document into some other format by using rules to execute another tool. Creating a similar task in Ant is more complex: a separate task must be written in Java and included with the Ant build file in order to handle the same type of functionality. However, this separation can enhance the readability of the Ant script by hiding some of the details of how a task is executed on different platforms.
There exist myriad third-party Ant extensions (called antlibs) that provide much of the missing functionality. Also, the Eclipse integrated development environment (IDE) can build and execute Ant scripts, while the NetBeans IDE uses Ant for its internal build system. As both these IDEs are very popular development platforms, they can simplify Ant use significantly. (As a bonus, Ant scripts generated by NetBeans can be used outside that IDE as standalone scripts.)
- Build automation
- Apache Jelly, a tool for turning XML into executable code
- Apache Ivy, a dependency manager which integrates tightly with Ant, subproject of Ant
- Apache Maven, a project management and build automation tool primarily for Java
- Nant, Ant-like tool targeted at the .NET Framework environment rather than Java
- Gradle, a JVM build tool built with Groovy
- "Apache Ant Project News". Retrieved 5 September 2018.
- "What's Wrong With GNU make? - Conifer Systems".
- "Why do you call it Ant? – Apache Ant FAQ".
- MacNeill, Conor. "The Early History of Ant Development".
- Wiley (2002). Java Tools for eXtreme Programming. p. 76.
- "WOProject-Ant – WOProject / WOLips – Confluence". Archived from the original on 2009-01-08.
- "Ant-Contrib Tasks".
- "Overview of Ant Tasks".
- Loughran, Steve; Hatcher, Erik (July 12, 2007). Ant in Action (2nd ed.). Manning Publications. p. 600. ISBN 978-1-932394-80-1.
- Holzner, Steven (April 13, 2005). Ant – The Definitive Guide (2nd ed.). O'Reilly Media. p. 334. ISBN 978-0-596-00609-9.
- Moodie, Matthew (November 16, 2005). Pro Apache Ant (1st ed.). Apress. p. 360. ISBN 978-1-59059-559-6.
- Bell, Alexis T. (July 7, 2005). ANT Java Notes: An Accelerated Intro Guide to the Java ANT Build Tool (1st ed.). Virtualbookworm.com Publishing. p. 268. ISBN 978-1-58939-738-5.
- Hatcher, Erik; Loughran, Steve (August 2002). Java Development with Ant (1st ed.). Manning Publications. p. 672. ISBN 978-1-930110-58-8.
- Niemeyer, Glenn; Poteet, Jeremy (May 29, 2003). Extreme Programming with Ant: Building and Deploying Java Applications with JSP, EJB, XSLT, XDoclet, and JUnit (1st ed.). SAMS Publishing. p. 456. ISBN 978-0-672-32562-5.
- Williamson, Alan (November 1, 2002). Ant – Developer's Handbook (1st ed.). SAMS Publishing. p. 456. ISBN 978-0-672-32426-0.
- Matzke, Bernd (September 2003). ANT: The Java Build Tool In Practice (1st ed.). Charles River Media. p. 280. ISBN 978-1-58450-248-7.
|Wikibooks has a book on the topic of: Apache Ant|