Luckily, there is a nice open source solution called XmlTask, which offers many possibilities to work with XML files.

1. Download the latest version of XmlTask from http://xmltask.sf.net
2. Create a task definition in Ant

   1 2 3 4

   <taskdef name="xmltask" classname="com.oopsconsultancy.xmltask.ant.XmlTask" classpath="./xmltask-v1.15.1.jar" />

3. Use it with the <xmltask> definition
   
   For example, read out the number of a specific node in the XML file:

   1 2 3

   <xmltask source="someFile.xml"> <copy path="count(//aNode)" property="numberOfNodes" /> </xmltask>

   Or change an attribute:

   1 2 3

   <xmltask source="someFile.xml" dest="toAnotherFile.xml"> <attr path="//aNode[1]" attr="enabled" value="true"/> </xmltask>

There are many other possibilites to work with XML files inside Ant. Check out the documentation at http://xmltask.sf.net.

But fortunately, there is Groovy. Groovy is a scripting language, which runs in a Java Virtual Machine. And because of that, it can be easily integrated with Ant.

1. Download the latest release of Groovy at http://groovy.codehaus.org/Download
2. Inside the Groovy binary, there is a folder called embeddable. In this folder, there is a file called groovy-all-X.X.X.jar. Take it and copy it near your build file.
3. Create a task definition in Ant

   1 2 3 4

   <taskdef name="groovy" classpath="./groovy-all-X.X.X.jar" classname="org.codehaus.groovy.ant.Groovy" />

4. Use Groovy somewhere inside an Ant task:
   

   1 2 3 4 5 6 7 8 9

   <groovy> int i = 1 int numberOfIterations = properties["numberOfIterations"].toInteger() while (i &lt;= numberOfIterations) { properties["currentIteration"] = i ant.antcall(target:"execute.a.task") i++ } </groovy>

Isn’t that groovy?

Groovy integrated in Ant offers many possibilities, which can be read here http://groovy.codehaus.org/The+groovy+Ant+Task. I used for my little script the variable ant, an instance of the current Ant project and the properties map, which holds all properties inside Ant.

<taskdef resource="net/sf/antcontrib/antcontrib.properties"></taskdef>

Now, you can start using constructs like if, foreach and combine these tasks with usual ANT tasks. Here a little example:

with antcontrib:

<target name="theultimateconditionmachine">
  <if>
    <equals arg1="${foo}" arg2="bar" />
    <then>
      <echo message="property foo is bar" />
    </then>
    <else>
      <echo message="property foo is not bar" />
    </else>
  </if>
</target>

without antcontrib:
if you want to perform the same task with ant, you need to create 4 (!) ant targets:

<target name="noway">
  <antcall target="conditionIf"/>
  <antcall target="conditionElse"/>
</target>
 
<target name="conditionDef">
  <condition property="conditionIsTrue">
    <equals arg1="${foo}" arg2="bar"/>
  </condition>
</target>
 
<target name="conditionIf" depends="conditionDef" if="conditionIsTrue">
  <echo message="property foo is bar"/>
</target>
 
<target name="conditionElse" depends="conditionDef" unless="conditionIsTrue">
  <echo message="property foo is not bar"/>
</target>