At 14:23 16/08/2001 -0700, Sanjay Bhatia wrote:
I'm interested in seeing examples
of buildfiles that work well for you and
those that you would consider very well organized. If you have
NDA issues to deal with please ignore this. Feel free to email me
There are some confidentiality issues which mean I don't feel comfortable
with releasing the files directly. I can describe some details
We've factored out a number of utility targets into a common file
(Common.xml) which is included in all our other files using a standard
XML trick involving entity definitions. (Search the archive for
The targets within each file are systematically named. For example, we've
termed each collection of related builds a "block".
Inside block.ant you will find these targets:
block.build.nnnnn - Do a production build of this block at version
block.src.nnnnn - Retrieve all the source code of this block at version
block.compile - compile the source code for this block
block.document - document the source code for this block
block.src.files - fileset listing all source directories
This structure makes it easy to manage file maintenance.
Eg: to add a new version of the block, we don't have to guess the names
of the targets required. Invoking builds in other blocks (eg for core
functionality) is easy because all blocks use the same system.
Feel free to ask questions and I'll answer the best I can.
Hope this helps,
is an Art Form that Fights Back"
communication is confidential to ACT Financial
Systems (Asia Pacific) and is intended for use only by
the addressee. The views and opinions
expressed in this email are the senders own and do not
represent the views and opinions of
ACT Financial Systems (Asia Pacific).
Senior OO Analyst, ACT Financial Systems