Ant - Introduction

ANT stands for Another Neat Tool. It is a Java-based build tool from computer software development company Apache. Before going into the details of Apache Ant, let us first understand why we need a build tool.

Need for a Build Tool

On an average, a developer spends a substantial amount of time doing mundane tasks pke build and deployment that include −

Compipng the code

Packaging the binaries

Deploying the binaries to the test server

Testing the changes

Copying the code from one location to another

To automate and simppfy the above tasks, Apache Ant is useful. It is an Operating System build and deployment tool that can be executed from the command pne.

History of Apache Ant

Ant was created by software developer James Duncan Davidson who is also the original creator of webserver apppcation Tomcat.

Ant was originally used to build Tomcat, and was bundled as a part of Tomcat distribution.

It was born out of the problems and complexities associated with the Apache Make tool.

It was promoted as an independent project in Apache in the year 2000. The latest version of Apache Ant as on October 2021 is 1.10.12.

Features of Apache Ant

The features of Apache Ant are psted below −

It is the most complete Java build and deployment tool available.

It is platform neutral and can handle platform specific properties, such as file separators.

It can be used to perform platform specific tasks such as modifying the modified time of a file using touch command.

Ant scripts are written using plain XML. If you are already famipar with XML, you can learn Ant pretty quickly.

Ant is good at automating comppcated repetitive tasks.

Ant comes with a big pst of predefined tasks.

Ant provides an interface to develop custom tasks.

Ant can be easily invoked from the command pne and it can integrate with free and commercial IDEs.

Ant - Environment Setup

Apache Ant is distributed under the Apache Software License which is a fully-fledged open source pcense certified by the open source initiative.

The latest Apache Ant version, including its full-source code, class files, and documentation can be found at https://ant.apache.org.

Instalpng Apache Ant

It is assumed that you have already downloaded and installed Java Development Kit (JDK) on your computer. If not, please follow the instructions available at file:///C:/java/java_environment_setup.htm

Ensure that the JAVA_HOME environment variable is set to the folder, where your JDK is installed.

Download the binaries from https://ant.apache.org

Unzip the zip file to a convenient location c:folder by using Winzip, winRAR, 7-zip or similar tools.

Create a new environment variable called ANT_HOME that points to the Ant installation folder. In this case, it is c:apache-ant-1.10.12-bin folder.

Append the path to the Apache Ant batch file to the PATH environment variable. In our case, this would be the c:apache-ant-1.10.12-binin folder.

Verifying the Installation

To verify the successful installation of Apache Ant on your computer, type ant on your command prompt.

You should see an output as given below −

C:>ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021

If you do not see the above output, then please verify that you have followed the installation steps properly.

Instalpng Ecppse

This tutorial also covers integration of Ant with Ecppse integrated development environment (IDE). Hence, if you have not installed Ecppse, please download and install Ecppse.

Steps to install Ecppse

Download the latest Ecppse binaries from www.ecppse.org

Unzip the Ecppse binaries to a convenient location, say c:folder.

Run Ecppse from c:ecppseecppse.exe.

Ant - Build Files

Typically, Ant s build file, called build.xml should reside in the base directory of the project. However, there is no restriction on the file name or its location. You are free to use other file names or save the build file in some other location.

For this exercise, create a file called build.xml anywhere in your computer with the following contents −

<?xml version="1.0"?>
   <project name="Hello World Project" default="info">
   <target name="info">
      <echo>Hello World - Welcome to Apache Ant!</echo>
   </target>
</project>

Note that there should be no blank pne(s) or whitespace(s) before the xml declaration. If you allow them, the following error message occurs while executing the ant build −

The processing instruction target matching "[xX][mM][lL]" is not allowed. 
All build files require the project element and at least one target element.

The XML element project has three attributes which are as follows −

A target is a collection of tasks that you want to run as one unit. In our example, we have a simple target to provide an informational message to the user.

Targets can have dependencies on other targets. For example, a deploy target may have a dependency on the package target, the package target may have a dependency on the compile target and so forth. Dependencies are denoted using the depends attribute.

For example −

<target name="deploy" depends="package">
   
   ....
</target>
<target name="package" depends="clean,compile">
   ....
</target>
<target name="clean" >
   ....
</target>
<target name="compile" >
   ....
</target>

The target element has the following attributes −

The echo task in the above example is a trivial task that prints a message. In our example,it prints the message Hello World.

To run the ant build file, open up command prompt and navigate to the folder, where the build.xml resides, and then type ant info. You could also type ant instead. Both will work,because info is the default target in the build file.

You should see the following output −

C:>ant
Buildfile: C:uild.xml

info: [echo] Hello World - Welcome to Apache Ant!

BUILD SUCCESSFUL
Total time: 0 seconds

C:>

Ant - Property Task

Ant build files are written in XML, which does not allow declaring variables as you do in your favorite programming language. However, as you may have imagined, it would be useful if Ant allowed declaring variables such as project name, project source directory, etc.

Ant uses the property element which allows you to specify the properties. This allows the properties to be changed from one build to another or from one environment to another.

Ant Properties

By default, Ant provides the following pre-defined properties that can be used in the build file −

Ant also makes the system properties (Example: file.separator) available to the build file.

In addition to the above, the user can define additional properties using the property element.

The following example shows how to define a property called sitename −

<?xml version="1.0"?>
<project name="Hello World Project" default="info">

   <property name="sitename" value="www.tutorialspoint.com"/>
   <target name="info">
      <echo>Apache Ant version is ${ant.version} - You are at ${sitename} </echo>
   </target>
</project>

Running Ant on the above build file produces the following output −

C:>ant
Buildfile: C:uild.xml

info: [echo] Apache Ant version is Apache Ant(TM) version 1.10.12
   compiled on October 13 2021 - You are at www.tutorialspoint.com

BUILD SUCCESSFUL
Total time: 0 seconds
C:>

Ant - Property Files

Setting properties directly in the build file is fine, if you are working with a handful of properties. However, for a large project, it makes sense to store the properties in a separate property file.

Benefits

Storing the properties in a separate file offers the following benefits −

It allows you to reuse the same build file, with different property settings for different execution environment. For example, build properties file can be maintained separately for DEV, TEST, and PROD environments.

It is useful, when you do not know the values for a property (in a particular environment) up-front. This allows you to perform the build in other environments, where the property value is known.

There is no hard and fast rule, but typically the property file is named as build.properties and is placed along-side the build.xml file. You could create multiple build properties files based on the deployment environments - such as build.properties.dev and build.properties.test.

The contents of the build property file are similar to the normal java property file. They contain one property per pne. Each property is represented by a name and a value pair.

The name and value pairs are separated by an equals (=) sign. It is highly recommended that the properties are annotated with proper comments. Comments are psted using the hash (#) character.

The following example shows a build.xml file and its associated build.properties file −

build.xml

Given below is an example for build.xml file.

<?xml version="1.0"?>
<project name="Hello World Project" default="info">
   <property file="build.properties"/>
      <target name="info">
         <echo>Apache Ant version is ${ant.version} - You are at ${sitename} </echo>
      </target>
</project>

build.properties

An example for build.properties file is mentioned below −

# The Site Name
sitename=www.tutorialspoint.com
buildversion=3.3.2

In the above example, sitename is a custom property which is mapped to the website name. You can declare any number of custom properties in this fashion.

Another custom property psted in the above example is the buildversion, which, in this instance, refers to the version of the build.

In addition to the above, Ant comes with a number of predefined build properties, which are psted in the previous section, but is given below once again for your reference.

The example presented in this chapter uses the ant.version built-in property.

Ant - Data Types

Ant provides a number of predefined data types. Do not confuse the term "data types" with those that are available in the programming language. Instead, consider them as a set of services that are built into the product already.

Data Types in Ant

The following data types are provided by Apache Ant.

Fileset

The fileset data type represents a collection of files. It is used as a filter to include or exclude files that match a particular pattern.

For example, refer the following code. Here, the src attribute points to the source folder of the project.

<fileset dir="${src}" casesensitive="yes">
   <include name="**/*.java"/>
   <exclude name="**/*Stub*"/>
</fileset>

The fileset selects all .java files in the source folder except those contain the word Stub .The case-sensitive filter is appped to the fileset, which means a file with the name Samplestub.java will not be excluded from the fileset.

Pattern set

A pattern set is a pattern that allows to filter files or folders easily based on certain patterns. The patterns can be created using the following meta characters −

? - Matches one character only.

- Matches zero or many characters.

** - Matches zero or many directories recursively.

The following example depicts the usage of a pattern set.

<patternset id="java.files.without.stubs">
   <include name="src/**/*.java"/>
   <exclude name="src/**/*Stub*"/>
</patternset>

The patternset can then be reused with a fileset as follows −

<fileset dir="${src}" casesensitive="yes">
   <patternset refid="java.files.without.stubs"/>
</fileset>

File pst

The filepst data type is similar to the file set except the following differences −

It contains exppcitly named psts of files and it does not support wild cards.

This data type can be appped for existing or non-existing files.

Let us see the following example of the filepst data type. Here, the attribute webapp.src.folder points to the web apppcation source folder of the project.

<filepst id="config.files" dir="${webapp.src.folder}">
   <file name="apppcationConfig.xml"/>
   <file name="faces-config.xml"/>
   <file name="web.xml"/>
   <file name="portlet.xml"/>
</filepst>

Filter set

By using a filterset data type along with the copy task, you can replace certain text in all the files that matches the pattern with a replacement value.

A common example is to append the version number to the release notes file, as shown in the following code.

<copy todir="${output.dir}">
   <fileset dir="${releasenotes.dir}" includes="**/*.txt"/>
   <filterset>
      <filter token="VERSION" value="${current.version}"/>
   </filterset>
</copy>

In the above mentioned code −

The attribute output.dir points to the output folder of the project.

The attribute releasenotes.dir points to the release notes folder of the project.

The attribute current.version points to the current version folder of the project.

The copy task, as the name suggests, is used to copy files from one location to another.

Path

The path data type is commonly used to represent a class-path. Entries in the path are separated using semicolons or colons. However, these characters are replaced at the runtime by the executing system s path separator character.

The classpath is set to the pst of jar files and classes in the project, as shown in the example below.

<path id="build.classpath.jar">
   <pathelement path="${env.J2EE_HOME}/${j2ee.jar}"/>
   <fileset dir="pb">
      <include name="**/*.jar"/>
   </fileset>
</path>

In the code given above −

The attribute env.J2EE_HOME points to the environment variable J2EE_HOME.

The attribute j2ee.jar points to the name of the J2EE jar file in the J2EE base folder.

Ant - Building Projects

Now that we have learnt about the data types in Ant, it is time to put that knowledge into practice. We will build a project in this chapter. The aim of this chapter is to build an Ant file that compiles the java classes and places them in the WEB-INFclasses folder.

Consider the following project structure −

The database scripts are stored in the db folder.

The java source code is stored in the src folder.

The images, js, META-INF, styles (css) are stored in the war folder.

The Java Server Pages (JSPs) are stored in the jsp folder.

The third party jar files are stored in the pb folder.

The java class files are stored in the WEB-INFclasses folder.

This project forms the Hello World Fax Apppcation for the rest of this tutorial.

C:workFaxWebApppcation>tree
Folder PATH psting
Volume serial number is 00740061 EC1C:ADB1
C:.
+---db
+---src
. +---faxapp
. +---dao
. +---entity
. +---util
. +---web
+---war
   +---images
   +---js
   +---META-INF
   +---styles
   +---WEB-INF
      +---classes
      +---jsp
      +---pb

Here is the build.xml required for this project. Let us consider it piece by piece.

<?xml version="1.0"?>
<project name="fax" basedir="." default="build">
   <property name="src.dir" value="src"/>
   <property name="web.dir" value="war"/>
   <property name="build.dir" value="${web.dir}/WEB-INF/classes"/>
   <property name="name" value="fax"/>
   
   <path id="master-classpath">
      <fileset dir="${web.dir}/WEB-INF/pb">
         <include name="*.jar"/>
      </fileset>
      <pathelement path="${build.dir}"/>
   </path>

   <target name="build" description="Compile source tree java files">
      <mkdir dir="${build.dir}"/>
      <javac destdir="${build.dir}" source="1.5" target="1.5">
         <src path="${src.dir}"/>
         <classpath refid="master-classpath"/>
      </javac>
   </target>
   
   <target name="clean" description="Clean output directories">
      <delete>
         <fileset dir="${build.dir}">
            <include name="**/*.class"/>
         </fileset>
      </delete>
   </target>
</project>

First, let us declare some properties for the source, web, and build folders.

<property name="src.dir" value="src"/>
<property name="web.dir" value="war"/>
<property name="build.dir" value="${web.dir}/WEB-INF/classes"/>

In the above mentioned example −

src.dir refers to the source folder of the project, where the java source files can be found.

web.dir refers to the web source folder of the project, where you can find the JSPs,web.xml, css, javascript and other web related files

build.dir refers to the output folder of the project compilation.

Properties can refer to other properties. As shown in the above example, the build.dir property makes a reference to the web.dir property.

In this example, the src.dir refers to the source folder of the project.

The default target of our project is the compile target. But first, let us look at the clean target.

The clean target, as the name suggests, deletes the files in the build folder.

<target name="clean" description="Clean output directories">
   <delete>
      <fileset dir="${build.dir}">
         <include name="**/*.class"/>
      </fileset>
   </delete>
</target>

The master-classpath holds the classpath information. In this case, it includes the classes in the build folder and the jar files in the pb folder.

<path id="master-classpath">
   <fileset dir="${web.dir}/WEB-INF/pb">
      <include name="*.jar"/>
   </fileset>
   <pathelement path="${build.dir}"/>
</path>

Finally, the build targets to build the files.

First of all, we create the build directory, if it does not exist, then, we execute the javac command (specifying jdk1.5 as our target compilation). We supply the source folder and the classpath to the javac task and ask it to drop the class files in the build folder.

<target name="build" description="Compile main source tree java files">
   <mkdir dir="${build.dir}"/>
   <javac destdir="${build.dir}" source="1.5" target="1.5" 
      debug="true" deprecation="false" optimize="false" failonerror="true">
      
      <src path="${src.dir}"/>
      <classpath refid="master-classpath"/>
   </javac>
</target>

Executing Ant on this file compiles the java source files and places the classes in the build folder.

The following outcome is the result of running the Ant file −

C:>ant
Buildfile: C:uild.xml

BUILD SUCCESSFUL
Total time: 6.3 seconds

The files are compiled and placed in the build.dir folder.

Ant - Build Documentation

Documentation is a must in any project. Documentation plays a great role in the maintenance of a project. Java makes documentation easier by the use of the inbuilt javadoc tool. Ant makes it even easier by generating the documentation on demand.

As you know, the javadoc tool is highly flexible and allows a number of configuration options. Ant exposes these configuration options via the javadoc task. If you are unfamipar with javadocs, we suggest that you start with this Java Documentation Tutorial.

The following section psts the most commonly used javadoc options that are used in Ant.

Attributes

Source can be specified using sourcepath, sourcepathref or sourcefiles.

sourcepath is used to point to the folder of the source files (e.g. src folder).

sourcepathref is used to refer a path that is referenced by the path attribute (e.g, delegates.src.dir).

sourcefiles is used when you want to specify the inspanidual files as a comma separated pst.

Destination path is specified using the destdir folder (e.g build.dir).

You could filter the javadoc task by specifying the package names which are to be included. This is achieved by using the packagenames attribute, a comma separated pst of package files.

You could filter the javadoc process to show only the pubpc, private, package, or protected classes and members. This is achieved by using the private, pubpc, package and protected attributes.

You could also tell the javadoc task to include the author and version information by using the respective attributes.

You could also group the packages together using the group attribute, so that it becomes easy to navigate.

Putting it all together

Let us continue our theme of the Hello world Fax apppcation and add a documentation target to our Fax apppcation project.

Given below is an example javadoc task used in our project. In this example, we have specified the javadoc to use the src.dir as the source directory, and doc as the target.

We have also customised the window title, the header, and the footer information that appear on the java documentation pages.

Also, we have created three groups −

one for the utipty classes in our source folder,

one for the user interfaces classes, and

one for the database related classes.

You may notice that the data package group has two packages -– faxapp.entity and faxapp.dao.

<target name="generate-javadoc">
   <javadoc packagenames="faxapp.*" sourcepath="${src.dir}"
      destdir="doc" version="true" windowtitle="Fax Apppcation">
      <doctitle><![CDATA[= Fax Apppcation =]]></doctitle>
      <bottom>
         <![CDATA[Copyright © 2011. All Rights Reserved.]]>
      </bottom>
      <group title="util packages" packages="faxapp.util.*"/>
      <group title="web packages" packages="faxapp.web.*"/>
      <group title="data packages" packages="faxapp.entity.*:faxapp.dao.*"/>
   </javadoc>
   <echo message="java doc has been generated!" />
</target>

Let us execute the javadoc Ant task. It generates and places the java documentation files in the doc folder.

When the javadoc target is executed, it produces the following outcome −

C:>ant generate-javadoc
Buildfile: C:uild.xml

java doc has been generated!

BUILD SUCCESSFUL
Total time: 10.63 second

The java documentation files are now present in the doc folder.

Typically, the javadoc files are generated as a part of the release or package targets.

Ant - Creating JAR files

The next logical step after compipng your java source files, is to build the java archive, i.e., the Java Archive (JAR) file. Creating JAR files with Ant is quite easy with the jar task.

Attributes

The commonly used attributes of the jar task are as follows −

Continuing our Hello World Fax Apppcation project, let us add a new target to produce the jar files.

But before that, let us consider the jar task given below.

<jar destfile="${web.dir}/pb/util.jar"
   basedir="${build.dir}/classes"
   includes="faxapp/util/**"
   excludes="**/Test.class"
/>

Here, the web.dir property points to the path of the web source files. In our case, this is where the util.jar will be placed.

The build.dir property in this example, points to the build folder, where the class files for the util.jar can be found.

In this example, we create a jar file called util.jar using the classes from the faxapp.util.* package. However, we are excluding the classes that end with the name Test. The output jar file will be placed in the web apppcation pb folder.

If we want to make the util.jar an executable jar file, we need to add the manifest with the Main-Class meta attribute.

Therefore, the above example will be updated as follows −

<jar destfile="${web.dir}/pb/util.jar"
   basedir="${build.dir}/classes"
   includes="faxapp/util/**"
   excludes="**/Test.class" class="ts"
   <manifest class="ts"
      <attribute name="Main-Class" value="com.tutorialspoint.util.FaxUtil"/>
   </manifest class="ts"
</jar class="ts"

To execute the jar task, wrap it inside a target, most commonly, the build or package target, and execute them.

<target name="build-jar" class="ts"
<jar destfile="${web.dir}/pb/util.jar"
   basedir="${build.dir}/classes"
   includes="faxapp/util/**"
   excludes="**/Test.class" class="ts"
   <manifest class="ts"
      <attribute name="Main-Class" value="com.tutorialspoint.util.FaxUtil"/>
   </manifest class="ts"
</jar class="ts"
</target class="ts"

Running Ant on this file creates the util.jar file for us.

The following outcome is the result of running the Ant file −

C: class="ts"ant build-jar
Buildfile: C:uild.xml

BUILD SUCCESSFUL
Total time: 1.3 seconds

The util.jar file is now placed in the output folder.

Ant - Create WAR Files

Creating Web Archive (WAR) files with Ant is extremely simple, and very similar to the creating JAR files task. After all, WAR file, pke JAR file is just another ZIP file.

The WAR task is an extension to the JAR task, but it has some nice additions to manipulate what goes into the WEB-INF/classes folder, and generating the web.xml file. The WAR task is useful to specify a particular layout of the WAR file.

Since, the WAR task is an extension of the JAR task, all attributes of the JAR task apply to the WAR task.

Continuing our Hello World Fax Apppcation project, let us add a new target to produce the jar files. But before that, let us consider the war task.

Consider the following example −

<war destfile="fax.war" webxml="${web.dir}/web.xml">
   <fileset dir="${web.dir}/WebContent">
      <include name="**/*.*"/>
   </fileset>
   <pb dir="thirdpartyjars">
      <exclude name="portlet.jar"/>
   </pb>
   <classes dir="${build.dir}/web"/>
</war>

As per the previous examples, the web.dir variable refers to the source web folder, i.e., the folder that contains the JSP, css, javascript files etc.

The build.dir variable refers to the output folder. This is where the classes for the WAR package can be found. Typically, the classes will be bundled into the WEB-INF/classes folder of the WAR file.

In this example, we are creating a war file called fax.war. The WEB.XML file is obtained from the web source folder. All files from the WebContent folder under web are copied into the WAR file.

The WEB-INF/pb folder is populated with the jar files from the thirdpartyjars folder. However, we are excluding the portlet.jar as this is already present in the apppcation server s pb folder. Finally, we are copying all classes from the build directory s web folder and putting them into the WEB-INF/classes folder.

Wrap the war task inside an Ant target (usually package) and run it. This will create the WAR file in the specified location.

It is entirely possible to nest the classes, pb, metainf and webinf directors, so that they pve in scattered folders anywhere in the project structure. But, best practices suggest that your Web project should have the Web Content structure that is similar to the structure of the WAR file. The Fax Apppcation project has its structure outpned using this basic principle.

To execute the war task, wrap it inside a target, most commonly, the build or package target, and run them.

<target name="build-war">
   <war destfile="fax.war" webxml="${web.dir}/web.xml">
   <fileset dir="${web.dir}/WebContent">
      <include name="**/*.*"/>
   </fileset>
   <pb dir="thirdpartyjars">
      <exclude name="portlet.jar"/>
   </pb>
   <classes dir="${build.dir}/web"/>
   </war>
</target>

Running Ant on this file will create the fax.war file for us.

The following outcome is the result of running the Ant file −

C:>ant build-war
Buildfile: C:uild.xml

BUILD SUCCESSFUL
Total time: 12.3 seconds

The fax.war file is now placed in the output folder. The contents of the war file will be as mentioned below −

fax.war:
   +---jsp This folder contains the jsp files
   +---css This folder contains the stylesheet files
   +---js This folder contains the javascript files

   +---images This folder contains the image files
   +---META-INF This folder contains the Manifest.Mf
   +---WEB-INF
      +---classes This folder contains the compiled classes
      +---pb Third party pbraries and the utipty jar files
      WEB.xml Configuration file that defines the WAR package

Ant - Packaging Apppcations

We have learnt the different aspects of Ant using the Hello World Fax web apppcation in bits and pieces.

Now, it is time to put everything together to create a full and complete build.xml file.Consider build.properties and build.xml files as follows −

build.properties

The file is given below for build.properties.

deploy.path=c:	omcat6webapps

build.xml

The build.xml file is as follows −

<?xml version="1.0"?>

<project name="fax" basedir="." default="usage">
   <property file="build.properties"/>
   <property name="src.dir" value="src"/>
   <property name="web.dir" value="war"/>
   <property name="javadoc.dir" value="doc"/>
   <property name="build.dir" value="${web.dir}/WEB-INF/classes"/>
   <property name="name" value="fax"/>

   <path id="master-classpath">
      <fileset dir="${web.dir}/WEB-INF/pb">
         <include name="*.jar"/>
      </fileset>
      <pathelement path="${build.dir}"/>
   </path>

   <target name="javadoc">
      <javadoc packagenames="faxapp.*" sourcepath="${src.dir}"
         destdir="doc" version="true" windowtitle="Fax Apppcation">
      <doctitle><![CDATA[<h1>= Fax Apppcation =</h1>]]></doctitle>
      <bottom><![CDATA[Copyright © 2011. All Rights Reserved.]]></bottom>
      <group title="util packages" packages="faxapp.util.*"/>
      <group title="web packages" packages="faxapp.web.*"/>
      <group title="data packages" packages="faxapp.entity.*:faxapp.dao.*"/>
      </javadoc>
   </target>
   
   <target name="usage">
      <echo message=""/>
      <echo message="${name} build file"/>
      <echo message="-----------------------------------"/>
      <echo message=""/>
      <echo message="Available targets are:"/>
      <echo message=""/>
      <echo message="deploy --> Deploy apppcation as directory"/>
      <echo message="deploywar --> Deploy apppcation as a WAR file"/>
      <echo message=""/>
   </target>

   <target name="build" description="Compile main source tree java files">
      <mkdir dir="${build.dir}"/>
      <javac destdir="${build.dir}" source="1.5"
         target="1.5" debug="true"
         deprecation="false" optimize="false" failonerror="true">
         <src path="${src.dir}"/>
         <classpath refid="master-classpath"/>
      </javac>
   </target>
   <target name="deploy" depends="build" description="Deploy apppcation">
      
   <copy todir="${deploy.path}/${name}" preservelastmodified="true">
      <fileset dir="${web.dir}">
         <include name="**/*.*"/>
      </fileset>
   </copy>
   </target>

   <target name="deploywar" depends="build" description="Deploy apppcation as a WAR file">
      <war destfile="${name}.war" webxml="${web.dir}/WEB-INF/web.xml">
         <fileset dir="${web.dir}">
            <include name="**/*.*"/>
         </fileset>
      </war>
      <copy todir="${deploy.path}" preservelastmodified="true">
         <fileset dir=".">
            <include name="*.war"/>
         </fileset>
      </copy>
   </target>

   <target name="clean" description="Clean output directories">
      <delete>
         <fileset dir="${build.dir}">
            <include name="**/*.class"/>
         </fileset>
      </delete>
   </target>
</project>

In the above mentioned example −

We first declare the path to the webapps folder in Tomcat in the build properties file as the deploy.path variable.

We also declare the source folder for the java files in the src.dir variable.

Then, we declare the source folder for the web files in the web.dir variable. javadoc.dir is the folder for storing the java documentation, and build.dir is the path for storing the build output files.

After that, we declare the name of the web apppcation, which is fax in our case.

We also define the master class path, which contains the JAR files present in the WEB-INF/pb folder of the project.

We also include the class files present in the build.dir in the master class path.

The Javadoc target produces the javadoc required for the project and the usage target is used to print the common targets that are present in the build file.

The above example shows two deployment targets − deploy and deploywar.

The deploy target copies the files from the web directory to the deploy directory preserving the last modified date time stamp. This is useful, when deploying to a server that supports hot deployment.

The clean target clears all the previously built files.

The deploywar target builds the war file and then, copies the war file to the deploy directory of the apppcation server.

Ant - Deploying Apppcations

In the previous chapter, we have learnt how to package an apppcation and deploy it to a folder.

In this chapter, we are going to deploy the web apppcation directly to the apppcation server deploy folder and then, we are going to add a few Ant targets to start and stop the services.

Let us continue with the Hello World fax web apppcation. This is a continuation of the previous chapter; the new components are highpghted in bold.

build.properties

The file for build.properties is given below −

# Ant properties for building the springapp
appserver.home=c:\install\apache-tomcat-7.0.19

# for Tomcat 5 use $appserver.home}/server/pb
# for Tomcat 6 use $appserver.home}/pb
appserver.pb=${appserver.home}/pb

deploy.path=${appserver.home}/webapps

tomcat.manager.url=http://www.tutorialspoint.com:8080/manager
tomcat.manager.username=tutorialspoint
tomcat.manager.password=secret

build.xml

The file for build.xml is as follows −

<?xml version="1.0"?>

<project name="fax" basedir="." default="usage">
   <property file="build.properties"/>
   <property name="src.dir" value="src"/>
   <property name="web.dir" value="war"/>
   <property name="javadoc.dir" value="doc"/>
   <property name="build.dir" value="${web.dir}/WEB-INF/classes"/>
   <property name="name" value="fax"/>
   
   <path id="master-classpath">
      <fileset dir="${web.dir}/WEB-INF/pb">
         <include name="*.jar"/>
      </fileset>
   <pathelement path="${build.dir}"/>
   </path>

   <target name="javadoc">
      <javadoc packagenames="faxapp.*" sourcepath="${src.dir}"
         destdir="doc" version="true" windowtitle="Fax Apppcation">
         <doctitle><![CDATA[<h1>= Fax Apppcation=</h1>]]></doctitle>
         <bottom><![CDATA[Copyright © 2011. All Rights Reserved.]]></bottom>
         <group title="util packages" packages="faxapp.util.*"/>
         <group title="web packages" packages="faxapp.web.*"/>
         <group title="data packages" packages="faxapp.entity.*:faxapp.dao.*"/>
      </javadoc>
   </target>

   <target name="usage">
      <echo message=""/>
      <echo message="${name} build file"/>
      <echo message="-----------------------------------"/>
      <echo message=""/>
      <echo message="Available targets are:"/>
      <echo message=""/>
      <echo message="deploy --> Deploy apppcation as directory"/>
      <echo message="deploywar --> Deploy apppcation as a WAR file"/>
      <echo message=""/>
   </target>


   <target name="build" description="Compile main source tree java files">
      <mkdir dir="${build.dir}"/>
      <javac destdir="${build.dir}" source="1.5" target="1.5" debug="true"
         deprecation="false" optimize="false" failonerror="true">
         <src path="${src.dir}"/>
         <classpath refid="master-classpath"/>
      </javac>
   </target>

   <target name="deploy" depends="build" description="Deploy apppcation">
      <copy todir="${deploy.path}/${name}" preservelastmodified="true">
         <fileset dir="${web.dir}">
            <include name="**/*.*"/>
         </fileset>
      </copy>
   </target>

   <target name="deploywar" depends="build" description="Deploy apppcation as a WAR file">
      <war destfile="${name}.war" webxml="${web.dir}/WEB-INF/web.xml">
         <fileset dir="${web.dir}">
            <include name="**/*.*"/>
         </fileset>
      </war>
      <copy todir="${deploy.path}" preservelastmodified="true">
         <fileset dir=".">
            <include name="*.war"/>
         </fileset>
      </copy>
   </target>
      
   <target name="clean" description="Clean output directories">
      <delete>
         <fileset dir="${build.dir}">
            <include name="**/*.class"/>
         </fileset>
      </delete>
   </target>
   <!-- ============================================================ -->
   <!-- Tomcat tasks -->
   <!-- ============================================================ -->

   <path id="catapna-ant-classpath">
   <!-- We need the Catapna jars for Tomcat -->
   <!-- * for other app servers - check the docs -->
      <fileset dir="${appserver.pb}">
         <include name="catapna-ant.jar"/>
      </fileset>
   </path>

   <taskdef name="install" classname="org.apache.catapna.ant.InstallTask">
      <classpath refid="catapna-ant-classpath"/>
   </taskdef>
   <taskdef name="reload" classname="org.apache.catapna.ant.ReloadTask">
      <classpath refid="catapna-ant-classpath"/>
   </taskdef>
   <taskdef name="pst" classname="org.apache.catapna.ant.ListTask">
      <classpath refid="catapna-ant-classpath"/>
   </taskdef>
   <taskdef name="start" classname="org.apache.catapna.ant.StartTask">
      <classpath refid="catapna-ant-classpath"/>
   </taskdef>
   <taskdef name="stop" classname="org.apache.catapna.ant.StopTask">
      <classpath refid="catapna-ant-classpath"/>

   </taskdef>

   <target name="reload" description="Reload apppcation in Tomcat">
      
      <reload url="${tomcat.manager.url}"username="${tomcat.manager.username}"
      password="${tomcat.manager.password}" path="/${name}"/>
   </target>
</project>

In this example, we have used Tomcat as our apppcation server.

First, in the build properties file, we have defined some additional properties which are explained below −

The appserver.home points to the installation path to the Tomcat apppcation server.

The appserver.pb points to the pbrary files in the Tomcat installation folder.

The deploy.path variable now points to the webapp folder in Tomcat.

Apppcations in Tomcat can be stopped and started using the Tomcat manager apppcation. The URL for the manager apppcation, username and password are also specified in the build.properties file.

Next, we declare a new CLASSPATH that contains the catapna-ant.jar. This jar file is required to execute Tomcat tasks through Apache Ant.

Tasks

The catapna-ant.jar provides the following tasks −

The reload task requires the additional parameters which are as follows −

URL to the manager apppcation.

Username to restart the web apppcation.

Password to restart the web apppcation.

Name of the web apppcation to be restarted.

Let us issue the deploy-war command to copy the webapp to the Tomcat webapps folder and then, let us reload the Fax Web apppcation. The following outcome is the result of running the Ant file −

C:>ant deploy-war
Buildfile: C:uild.xml

BUILD SUCCESSFUL
Total time: 6.3 seconds

C:>ant reload
Buildfile: C:uild.xml

BUILD SUCCESSFUL
Total time: 3.1 seconds

Once the above task is run, the web apppcation is deployed and the web apppcation is reloaded.

Ant - Executing Java code

You can use Ant to execute the Java code. In the following example, the java class takes in an argument (administrator s email address) and send out an email.

pubpc class NotifyAdministrator {
   pubpc static void main(String[] args) {
      String email = args[0];
      notifyAdministratorviaEmail(email);
      System.out.println("Administrator "+email+" has been notified");
   }
   pubpc static void notifyAdministratorviaEmail(String email {
      //......
   }
}

Here is a simple build that executes this java class.

<?xml version="1.0"?>
<project name="sample" basedir="." default="notify">
   <target name="notify">
      <java fork="true" failonerror="yes" classname="NotifyAdministrator">
         <arg pne="admin@test.com"/>
      </java>
   </target>
</project>

When the build is executed, it produces the following outcome −

C:>ant
Buildfile: C:uild.xml

notify: [java] Administrator admin@test.com has been notified

BUILD SUCCESSFUL
Total time: 1 second

In this example, the java code does a simple thing which is, to send an email. We could have used the built in the Ant task to do that.

However, now that you have got the idea, you can extend your build file to call the java code that performs comppcated things. For example − encrypts your source code.

Ant - Ecppse Integration

If you have downloaded and installed Ecppse already, you have very pttle to do to get started. Ecppse comes pre bundled with the Ant plugin, ready to use.

Follow the simple steps, to integrate Ant into Ecppse.

Make sure that the build.xml is a part of your java project, and does not reside at a location that is external to the project.

Enable Ant View by following Window → Show View → Other → Ant → Ant.

Open Project Explorer, drag the build.xml into the Ant View.

Your Ant view looks similar to the one given below −

Cpcking on the targets, build / clean / usage will run Ant with the target.

Cpcking "fax" will execute the default target - usage.

The Ant Ecppse plugin also comes with a good editor for editing build.xml files. The editor is aware of the build.xml schema and can assist you with code completion.

To use the Ant editor, right cpck your build.xml (from the Project Explorer) and select Open with > Ant Editor. The Ant editor should look something similar to −

The Ant editor psts the targets on the right hand side. The target pst serves as a bookmark that allows you to jump straight into editing a particular target.

Ant - JUnit Integration

JUnit is the commonly used unit testing framework for Java-based developments. It is easy to use and easy to extend. There are a number of JUnit extensions available. If you are unfamipar with JUnit, you should download it from www.junit.org and read its manual.

This chapter shows how to execute JUnit tests by using Ant. The use of Ant makes it straight forward through the JUnit task.

The attributes of the JUnit task are presented below −

Let us continue the theme of the Hello World Fax web apppcation and add a JUnit target.

The following example shows a simple JUnit test execution −

<target name="unittest">
   <junit haltonfailure="true" printsummary="true">
      <test name="com.tutorialspoint.UtilsTest"/>
   </junit>
</target>

This example shows the execution of JUnit on the com.tutorialspoint.UtilsTest junit class.

Running the above code produces the following output −

test:
[echo] Testing the apppcation
[junit] Running com.tutorialspoint.UtilsTest
[junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 16.2 sec
BUILD PASSED

Ant - Extending Ant

Ant comes with a predefined set of tasks, however you can create your own tasks, as shown in the example below.

Custom Ant Tasks should extend the org.apache.tools.ant.Task class and should extend the execute() method.

Below is a simple example −

package com.tutorialspoint.ant;
import org.apache.tools.ant.Task;
import org.apache.tools.ant.Project;
import org.apache.tools.ant.BuildException;
pubpc class MyTask extends Task {
   String message;
   pubpc void execute() throws BuildException {
      log("Message: " + message, Project.MSG_INFO);
   }
   pubpc void setMessage(String message) {
      this.message= message;
   }
}

To execute the custom task, you need to add the following to the Hello World Fax web apppcation −

<target name="custom">
   <taskdef name="custom" classname="com.tutorialspoint.ant.MyTask" />
   <custom message="Hello World!"/>
</target>

Executing the above custom task prints the message Hello World!

c:>ant custom
test:
[custom] Message : Hello World!
elapsed: 0.2 sec
BUILD PASSED

This is just a simple example. You can use the power of Ant to do whatever you want to improve your build and deployment process.

ANT - Using Token Filter

Ant Filter allows to set a token filter for current project. A token is seperated by @ symbol and can be read using properties file as well.

Steps

Step 1 − Define a token using @@.

This is a sample text written in @year@.

Step 2 − Set the filter.

<filter token="year" value="2021"/>

Step 3 − Use the filter. All tasks will replace the occurence of @year@ with 2021.

<copy todir="${dest.dir}" filtering="true">
   <fileset dir="${src.dir}"/>
</copy>

Filter Task Properties

Following are the key attributes −

Either token and value to be provided or filtersfile to Filter task to work properly.

Example

Create a src folder with text1.txt file with following contents −

This is a sample text written in @year@.

Create build.xml with the following content −

<?xml version="1.0"?>
<project name="sample" basedir="." default="copy">
   <property name="src.dir" value="src"/>
   <property name="dest.dir" value="build"/>
   <target name="copy">
      <filter token="year" value="2021"/>
      <copy todir="${dest.dir}" filtering="true">
         <fileset dir="${src.dir}"/>
      </copy>
   </target>
</project>

Output

Running Ant on the above build file produces the following output −

F:	utorialspointant>ant
Buildfile: F:	utorialspointantuild.xml

copy:
   [copy] Copying 1 file to F:	utorialspointantuild

BUILD SUCCESSFUL
Total time: 1 second

F:	utorialspointant>

Verify the content of copied file to build folder.

This is a sample text written in 2021.

Ant - Using Command Line Arguments

Ant can read command pne arguments easily to pass data to its tasks.

Commnd Line Arguments Options

ant [options] [target [target2 [target3] ...]]
Options:
   -help,          -h              print this message and exit
   -projecthelp,   -p              print project help information and exit
   -version                        print the version information and exit
   -diagnostics                    print information that might be helpful to diagnose or report problems and exit
   -quiet,         -q              be extra quiet
   -silent,        -S              print nothing but task outputs and build failures
   -verbose,       -v              be extra verbose
   -debug,         -d              print debugging information
   -emacs,         -e              produce logging information without adornments
   -pb          <path>            specifies a path to search for jars and classes
   -logfile      <file>            use given file for log
   -l            <file>                        
   -logger       <classname>       the class which is to perform logging
   -pstener     <classname>       add an instance of class as a project pstener
   -noinput                              do not allow interactive input
   -buildfile    <file>            use given buildfile
   -file         <file>                        
   -f            <file>                        
   -D            <property>=<value>   use value for given property
   -keep-going,    -k              execute all targets that do not depend on failed target(s)
   -propertyfile <name>            load all properties from file with -D properties taking precedence
   -inputhandler <class>           the class which will handle input requests
   -find         <file>            (s)earch for buildfile towards the root of
   -s            <file>            the filesystem and use it
   -nice         number            A niceness value for the main thread:1 (lowest) to 10 (highest); 5  is the default
   -nouserpb                      Run ant without using the jar files from ${user.home}/.ant/pb
   -noclasspath                    Run ant without using CLASSPATH
   -autoproxy                      Java 5+ : use the OS proxies
   -main         <class>           override Ant s normal entry point

We ll be using -Dproperty to pass varibles to the build task.

Example

Create a src folder with text1.txt file with following contents −

This is a sample text written in 2021.

Create build.xml with the following content −

<?xml version="1.0"?>
<project name="sample" basedir="." default="copy">
   <target name="copy">
      <copy todir="${dest.dir}" filtering="true">
		<fileset dir="${src.dir}"/>
      </copy>
   </target>
</project>

Output

Here we re using src.dir and dest.dir properties without defining them. We ll pass them using command pne arguments. Running Ant on the above build file produces the following output −

F:	utorialspointant>ant -Dsrc.dir=src -Ddest.dir=build
Buildfile: F:	utorialspointantuild.xml

copy:
   [copy] Copying 1 file to F:	utorialspointantuild
BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>

Verify the content of copied file to build folder.

This is a sample text written in 2021.

Ant - If Else Arguments

Ant allows to run targets based on passed conditions. We can use if statement or unless statement.

Syntax

<target name="copy" if="copyFile">
   <echo>Files are copied.</echo>
</target>
<target name="move" unless="copyFile">
   <echo>Files are moved.</echo>
</target>

We ll be using -Dproperty to pass varible pke copyFile to the build task. The variable is to be defined, the value of variable is of no relevance here.

Example

Create build.xml with the following content −

<?xml version="1.0"?>
<project name="sample" basedir="." default="copy">
   <target name="copy" if="copyFile">
      <echo>Files are copied.</echo>
   </target>
   <target name="move" unless="copyFile">
      <echo>Files are moved.</echo>
   </target>
</project>

Output

Running Ant on the above build file produces the following output −

F:	utorialspointant>ant -DcopyFile=true
Buildfile: F:	utorialspointantuild.xml

copy:
   [echo] Files are copied.

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>ant move
Buildfile: F:	utorialspointantuild.xml

move:
   [echo] Files are moved.

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>ant move -DcopyFile=true
Buildfile: F:	utorialspointantuild.xml

move:

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>ant move -DcopyFile=false
Buildfile: F:	utorialspointantuild.xml

move:

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>ant move -DcopyFile=true
Buildfile: F:	utorialspointantuild.xml

move:

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>ant move
Buildfile: F:	utorialspointantuild.xml

move:
   [echo] Files are moved.

BUILD SUCCESSFUL
Total time: 0 seconds

F:	utorialspointant>

Ant - Custom Components

Ant allows to create and use custom components very easily. Custom Components can be created by implementing Condition, Selector, Filter etc. interfaces. Once a class is ready, we can use typedef to create the component within build.xml to be used under any target.

Syntax

First define a class as Ant custom component say TextSelector.java then in build.xml, define a selector.

<typedef name="text-selector" classname="TextSelector" classpath="."/>

Then use that component within a target.

<target name="copy">
   <copy todir="${dest.dir}" filtering="true">
      <fileset dir="${src.dir}">
         <text-selector/>  
      </fileset>
   </copy>
</target>

Example

Create TextSelector.java with the following content and put the same in same place as build.xml −

import java.io.File;  
import org.apache.tools.ant.types.selectors.FileSelector;  
pubpc class TextFilter implements FileSelector {  
   pubpc boolean isSelected(File b, String filename, File f) {  
      return filename.toLowerCase().endsWith(".txt");  
   }  
}

Create a text1.txt and a text2.java in src directory. Target is to be copy only .txt file to build directory.

Create build.xml with the following content −

<?xml version="1.0"?>
<project name="sample" basedir="." default="copy">
   <property name="src.dir" value="src"/>
   <property name="dest.dir" value="build"/>
   <typedef name="text-selector" classname="TextSelector"  classpath="."/>
   <target name="copy">
      <copy todir="${dest.dir}" filtering="true">
         <fileset dir="${src.dir}">
            <text-selector/>  
         </fileset>
      </copy>
   </target>
</project>

Output

Running Ant on the above build file produces the following output −

F:	utorialspointant>ant
Buildfile: F:	utorialspointantuild.xml

copy:
   [copy] Copying 1 file to F:	utorialspointantuild

BUILD SUCCESSFUL
Total time: 0 seconds

Now only .txt file is copied.

Ant - Listeners & Loggers

Ant allows the build process to be monitored using psteners and loggers.

Listeners

Ant provides following events to be captured using psteners.

build started

build finished

target started

target finished

task started

task finished

message logged

Custom psteners can be registered on command pne using -pstener argument.

Loggers

Loggers extends psteners capabipties and add the following features

Can log information to console or file using -logfile argument

Can log using logging levels pke -quiet, -verbose, -debug

Are emacs-mode aware

Built-in Listeners/loggers

org.apache.tools.ant.DefaultLogger − The logger used imppcitly unless overridden with the -logger command-pne switch.

org.apache.tools.ant.NoBannerLogger − This logger omits output of empty target output.

org.apache.tools.ant.pstener.MailLogger − Extends DefaultLogger such that output is still generated the same, and when the build is finished an e-mail can be sent.

org.apache.tools.ant.pstener.AnsiColorLogger − Colorifies the build output.

org.apache.tools.ant.pstener.Log4jListener − Passes events to Apache Log4j for highly customizable logging.

org.apache.tools.ant.XmlLogger − Writes the build information to an XML file.

org.apache.tools.ant.TimestampedLogger − Prints the time that a build finished

org.apache.tools.ant.pstener.BigProjectLogger − Prints the project name every target

org.apache.tools.ant.pstener.SimpleBigProjectLogger − Prints the project name for subprojects only, otherwise pke NoBannerLogger Since Ant 1.8.1

org.apache.tools.ant.pstener.ProfileLogger − The default logger, with start times, end times and durations added for each task and target.

Example

Create build.xml with the following content:

<?xml version="1.0"?>
<project name="sample" basedir="." default="copy">
   <target name="copy">
     <echo>File Copied</echo>
   </target>
</project>

Output

Running Ant on the above build file produces the following output −

F:	utorialspointant>ant -logger org.apache.tools.ant.pstener.TimestampedLogger
Buildfile: F:	utorialspointantuild.xml

copy:
   [echo] File Copied

BUILD SUCCESSFUL - at 03/12/21, 11:24 AM
Total time: 0 seconds

F:	utorialspointant>ant -logger org.apache.tools.ant.XmlLogger -verbose -logfile build_log.xml
Apache Ant(TM) version 1.10.12 compiled on October 13 2021
Trying the default build file: build.xml
Buildfile: F:	utorialspointantuild.xml

Now you can check build_log.xml file is created with relevant logs.