ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject Re: Convention for laying out an ANT build script
Date Wed, 02 Apr 2003 14:30:31 GMT

You might try something like this...

Vizant is an Apache Ant task to visualize a buildfile using GraphViz or 
other drawing tools.

     <target name="vizAnt">
         <taskdef name="vizant" classname="net.sourceforge.vizant.Vizant" 
         <vizant antfile="build.xml" outfile=""/>
         <exec executable="dot" failifexecutionfails="false" 
resultproperty="graphvizSuccess!"><arg line="-Tpng -o 
         <fail unless="graphvizSuccess!">
         You probably need to install GraphViz which is a native program,
         not a Java library &gt;&gt;&gt;

Note the native program that you also need to install to get this working.


At 11:21 AM 4/2/2003 +1000, you wrote:
>I'm new to ANT. One thing I find difficult about ANT is tracing an ANT build
>script. Our company has a very long (500 lines) ANT script for build and
>deploy. However, whenever I need to trace through it to modify it, or debug
>it, I find myself jumping all over the build file because of dependencies.
>For this reason, using ANTCALL seemed like a better alternative. However, I
>have faced many problems using ANTCALL (particularly with properties). For
>some reason, properties declared in my init target are not accessed by
>targets called by ANTCALL unless the called target depends on the init
>What is the common convention for laying out an ANT build script? Build
>scripts can get awfully long... Is it a good or bad idea to have multiple
>ANT scripts so that files are smaller hence easier to manage?
>To unsubscribe, e-mail:
>For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message