ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patricia Watt" <>
Subject RE: Naming build files
Date Tue, 26 Nov 2002 17:40:50 GMT
We have separate build files for sub-components that get re-used in various independent components.
 We use the <ant> task to execute tasks from the sub-component build files, and it works
just fine.


-----Message d'origine-----
De : []
Envoyé : 26 novembre, 2002 12:31
À :
Objet : RE: Naming build files

I'm pleased to hear someone ask this question.

We're considering splitting our single build file into more manageable units as the size and
complexity of our project is now being reflected in a large and increasingly more complex
build file.

I like the prospect of using and embedding smaller build files using XML ENTITY include:-

Or, using the <ant> task to make calls to 'other' build files:-

Which may be the better option - given the apparent bugs in the XML ENTITY include method

In any event this modular approach does appear at first glance to offer some benefits - making
our build files smaller and more manageable, also a degree of modularity.  But from what Dominique
is saying there are also some issues to resolve.  Has anyone tried this and if so are there
any benefits? - I'd like to know before I split our buildfile up.



> -----Original Message-----
> From: Dominique Devienne []
> Sent: 26 November 2002 16:57
> To: 'Ant Users List'
> Subject: RE: Naming build files
> Indeed, so are the two build scripts I work on most usually. 
> But then if you
> use entity includes in your XML (see the FAQ), you expose 
> yourself to bugs
> in some tasks that do not resolve entity the same way as Ant 
> (AntDoc is one
> example, but there are others), which when cannot find the 
> entities and thus
> fail. I now always put my Ant build script at the top-level, 
> which is also
> the Best Practice in my opinion.
> So Stefan is right of course, but I do still recommend a 
> top-level build.xml
> If you decide otherwise, don't complain to me later is something's not
> working ;-) Cheers, --DD
> -----Original Message-----
> From: Stefan Bodewig [] 
> Sent: Tuesday, November 26, 2002 10:48 AM
> To:
> Subject: Re: Naming build files
> On Tue, 26 Nov 2002, Dominique Devienne <> wrote:
> > Putting the Ant build script at the top level is important, as
> > everything can then easily be defined relatively from this point
> > (see the location attribute of <property>).
> Actually it will be relative to the basedir attribute of your project
> element.
> "For historic reasons" the build.xml of the biggest CVS module in the
> company I work for is not at the top level but one level into the
> source tree - it has basedir=".." and so it is the same as if it was
> at the top level.
> Stefan
> --
> To unsubscribe, e-mail:   
> <>
> For additional commands, e-mail: 
> <>


For more information on HBOS Treasury Services, please visit

Or for details of our online FX & Deposit services, please go to

HBOS Treasury Services plc is part of the HBOS Group, which also includes Halifax plc and
Bank of Scotland.
Registered Office: 33 Old Broad Street, London EC2N 1HZ. Registered No. 2692890. Registered
in England.
Regulated by the Financial Services Authority.

The information contained in this message is confidential and is intended for the addressee
only. If you have received this message in error or there are any problems please notify the
originator immediately. The unauthorised use, disclosure, copying or alteration of this message
is strictly forbidden. This mail and any attachments have been scanned for viruses prior to
leaving the HBOS Treasury Services plc network. HBOS Treasury Services plc will not be liable
for direct, special, indirect or consequential damages arising from alteration of the contents
of this message by a third party or as a result of any virus being passed on.

HBOS Treasury Services plc reserves the right to monitor and record e-mail messages sent to
and from this address for the purposes of investigating or detecting any unauthorised use
of its system and ensuring its effective operation.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message