ANT

PATH- and CLASSPATH-type references can be specified using both ":" and ";" as separator characters. Ant converts the separator to the correct character of the current operating system.

<classpath>

<pathelement path="${classpath}"/>

<pathelement location="lib/helper.jar"/>

</classpath>

The location attribute specifies a single file or directory relative to the project's base directory (or an absolute filename)

The path attribute accepts colon- or semicolon-separated lists of locations. The path attribute is intended to be used with predefined paths - in any other case; multiple elements with location attributes should be preferred.

The <classpath> tag supports path and location attributes of its own:

<classpath path="${classpath}"/>

Before start using ant, we should be clear about the project name and the .java files and most importantly, the path where the .class files are to be placed.

For example, we want the application HelloWorld to be used with ant. The Java source files are in a subdirectory called Dirhelloworld, and the .class files are to put into a sub directory called Helloworldclassfiles.

1. The build file by name build.xml is to be written. The script is as follows

<project name=”HelloWorld” default=”compiler” basedir=”.”>

<target name=”compiler”>

<mkdir dir = “Helloworldclassfiles”>

<javac srcdir=”Dirhelloworld” destdir=”Helloworldclassfiles”>

</target>

</project>

2. Now run the ant script to perform the compilation:

C :> ant

Buildfile: build.xml

and see the results in the extra files and directory created:

c:>dir Dirhelloworld

c:>dir Helloworldclassfiles

All the .java files are in Dirhelloworld directory and all the corresponding .class are in Helloworldclassfiles directory.

Note: mkdir command is to be used in MS-DOS and mk dir command is to be used in UNIX/Linux

Dir command is to be used in MS-DOS and ls command is to be used in UNIX /Linux

Properties in ant are set in an order. Once a property is set, later the same property can not overwrite the previous one.

This process provides a good leverage of presetting all properties in one location, and overwriting only the needed properties. For instance, a password is to be used for an application task, and the developer does not want to share the password with his team members or developers of other teams. The following is the process to do the task:

- Store the password in ${user.home}/prj.properties file.

- Set the password – passwd = realpassword of the developer

- Master the prj.properties in include directory

passwd = password

- Read the property files in the following order in the build.xml file

1. Type ant –Dpasswd=newpassword

2. ${user.home}/prj.properties (personal)

3. projectdirectoryname/prj.properties (project team)

4. masterincludedirectory name/prj.properties (universal)

<cvsnttaskpasswd=${password=passwd} … />

Ant properties are immutable; they cannot be changed once initialized. However, it can be done in the following way although it causes the immutable property violation:

<?xml version="1.0"?>

<project name="example" default="run">

<taskdef name="groovy"

classname="org.codehaus.groovy.ant.Groovy"

classpath="lib/groovy-all-1.1-rc-1.jar"/>

<target name="run">

<echo>java.library.path = ${java.library.path}</echo>

<groovy>

properties["java.library.path"] = "changed"

</groovy>

<echo>java.library.path = ${java.library.path}</echo>

</target>

</project>