{"id":112,"date":"2026-10-12T07:52:16","date_gmt":"2026-10-12T07:52:16","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2009\/01\/28\/apache-ant-learn-apache-ant-from-ibm-experts\/"},"modified":"2026-10-12T07:52:16","modified_gmt":"2026-10-12T07:52:16","slug":"apache-ant-learn-apache-ant-from-ibm-experts","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/apache-ant-learn-apache-ant-from-ibm-experts\/","title":{"rendered":"Apache Ant for DevOps Engineers: Build Files, Dependencies, and Custom Tasks"},"content":{"rendered":"\n

Originally published on 2009-01-28; fully revised and updated.<\/em><\/p>\n\n\n\n

learn-apache-ant-from-experts<\/p>\n\n\n\n

Apache Ant is a Java-based build automation tool that defines repeatable build steps in XML. This guide is for engineers maintaining Java build pipelines who want a clear refresher on Ant fundamentals: build file anatomy, dependency-driven execution, command-line usage, packaging, filesystem operations, and custom task extension.<\/p>\n\n\n\n

Apache Ant at a glance<\/h2>\n\n\n\n

Ant is most useful when you need explicit control over build steps and cross-platform behavior without relying on shell-specific scripts. The original tutorial compared Ant to make; in modern teams, Ant is also often evaluated alongside Maven and Gradle.<\/p>\n\n\n\n

Tool<\/th>Configuration style<\/th>Typical strength<\/th>Common trade-off<\/th><\/tr><\/thead>
Ant<\/td>Explicit XML tasks and targets<\/td>Fine-grained control of build steps<\/td>Verbose configuration for large projects<\/td><\/tr>
Make<\/td>Rules plus shell commands<\/td>Simple and language-agnostic<\/td>Portability issues across shells and platforms<\/td><\/tr>
Maven<\/td>Convention-driven lifecycle and plugins<\/td>Standardized Java project structure<\/td>Less explicit control over each step<\/td><\/tr>
Gradle<\/td>Programmable DSL (Groovy or Kotlin)<\/td>Flexible build logic and ecosystem integration<\/td>Higher complexity for teams new to DSL-based builds<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Anatomy of a minimal build.xml<\/h2>\n\n\n\n

An Ant build file has one top-level project<\/strong>, with one or more target<\/strong> elements. Targets contain tasks<\/strong> (such as javac<\/code>, jar<\/code>, copy<\/code>, delete<\/code>) that perform the actual work.<\/p>\n\n\n

<?xml version='1.0'?><\/span>\n<project<\/span> name<\/span>='demo'<\/span> default<\/span>='hello'<\/span> basedir<\/span>='.'<\/span>><\/span>\n    <target<\/span> name<\/span>='hello'<\/span>><\/span>\n        <echo<\/span> message<\/span>='Hello from Ant'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Properties are immutable once set, and are typically used for paths and reusable values.<\/p>\n\n\n
<property<\/span> name<\/span>='src.dir'<\/span> location<\/span>='src'<\/span>\/><\/span>\n<property<\/span> name<\/span>='build.dir'<\/span> location<\/span>='build'<\/span>\/><\/span>\n\n<target<\/span> name<\/span>='compile'<\/span>><\/span>\n    <javac<\/span> srcdir<\/span>='${src.dir}'<\/span> destdir<\/span>='${build.dir}'<\/span> debug<\/span>='true'<\/span>\/><\/span>\n<\/target<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Dependency-driven build flow<\/h2>\n\n\n\n
Ant runs targets based on dependencies, not file order. If dist<\/code> depends on compile<\/code>, and compile<\/code> depends on init<\/code>, Ant resolves that chain automatically.<\/p>\n\n\n\n
\nflowchart TD\n    A[Run ant dist] --> B[Resolve dependencies]\n    B --> C[init target]\n    C --> D[compile target]\n    D --> E[dist target]\n    E --> F[Jar artifact in dist directory]\n<\/pre>\n\n\n
<target<\/span> name<\/span>='init'<\/span>><\/span>\n    <mkdir<\/span> dir<\/span>='build'<\/span>\/><\/span>\n<\/target<\/span>><\/span>\n\n<target<\/span> name<\/span>='compile'<\/span> depends<\/span>='init'<\/span>><\/span>\n    <javac<\/span> srcdir<\/span>='src'<\/span> destdir<\/span>='build'<\/span>\/><\/span>\n<\/target<\/span>><\/span>\n\n<target<\/span> name<\/span>='dist'<\/span> depends<\/span>='compile'<\/span>><\/span>\n    <jar<\/span> destfile<\/span>='dist\/app.jar'<\/span> basedir<\/span>='build'<\/span>\/><\/span>\n<\/target<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Running Ant from the command line<\/h2>\n\n\n\n
The default command is simply ant<\/code>, which executes the build file’s default target. You can then override file names, set properties, or call specific targets.<\/p>\n\n\n\n
Command or option<\/th>What it does<\/th>Example<\/th><\/tr><\/thead>
ant<\/td>Runs default target in build.xml<\/td>ant<\/td><\/tr>
-f or -buildfile<\/td>Uses a non-default build file name<\/td>ant -f build-prod.xml dist<\/td><\/tr>
-Dname=value<\/td>Sets a property before parsing build.xml<\/td>ant -Denv=staging clean dist<\/td><\/tr>
-p<\/td>Prints available targets<\/td>ant -p<\/td><\/tr>
target names<\/td>Runs one or more explicit targets<\/td>ant clean compile dist<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
ant\nant -f build.xml clean dist\nant -Dmetal=beryllium compile\nant -p<\/code><\/span><\/pre>\n\n\n
The original material also showed Eclipse integration (Ant editor, target execution, and console output). Those concepts remain useful, though exact UI steps vary by Eclipse version.<\/p>\n\n\n\n
Complete example: compile, package, and timestamp a Java build<\/h2>\n\n\n\n
This example mirrors the classic Ant workflow: initialize directories, compile Java sources, and create a date-stamped JAR.<\/p>\n\n\n
<project<\/span> name<\/span>='java-example'<\/span> default<\/span>='dist'<\/span> basedir<\/span>='.'<\/span>><\/span>\n    <description<\/span>><\/span>Simple Java project build<\/description<\/span>><\/span>\n\n    <property<\/span> name<\/span>='src.dir'<\/span> location<\/span>='src'<\/span>\/><\/span>\n    <property<\/span> name<\/span>='build.dir'<\/span> location<\/span>='build'<\/span>\/><\/span>\n    <property<\/span> name<\/span>='dist.dir'<\/span> location<\/span>='dist'<\/span>\/><\/span>\n\n    <target<\/span> name<\/span>='clean'<\/span>><\/span>\n        <delete<\/span> dir<\/span>='${build.dir}'<\/span>\/><\/span>\n        <delete<\/span> dir<\/span>='${dist.dir}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='init'<\/span>><\/span>\n        <tstamp<\/span>\/><\/span>\n        <mkdir<\/span> dir<\/span>='${build.dir}'<\/span>\/><\/span>\n        <mkdir<\/span> dir<\/span>='${dist.dir}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='compile'<\/span> depends<\/span>='init'<\/span>><\/span>\n        <javac<\/span> srcdir<\/span>='${src.dir}'<\/span> destdir<\/span>='${build.dir}'<\/span> debug<\/span>='true'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='dist'<\/span> depends<\/span>='compile'<\/span>><\/span>\n        <jar<\/span> destfile<\/span>='${dist.dir}\/package-${DSTAMP}.jar'<\/span> basedir<\/span>='${build.dir}'<\/span>><\/span>\n            <manifest<\/span>><\/span>\n                <attribute<\/span> name<\/span>='Main-Class'<\/span> value<\/span>='com.example.Main'<\/span>\/><\/span>\n            <\/manifest<\/span>><\/span>\n        <\/jar<\/span>><\/span>\n    <\/target<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n
ant clean dist\njava -jar dist\/package-*.jar<\/code><\/span><\/pre>\n\n\n
Filesystem tasks, patterns, and selectors<\/h2>\n\n\n\n
Ant includes strong cross-platform filesystem primitives. Common tasks include mkdir<\/code>, delete<\/code>, copy<\/code>, move<\/code>, zip<\/code>, jar<\/code>, and replace<\/code>. Pattern-based filesets and selectors let you work on groups of files safely and repeatably.<\/p>\n\n\n\n