Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337010472FC@mail.sandvine.com>
From: David McTavish <dmctavish@SANDVINE.com>
To: 'Ant Users List' <user@ant.apache.org>
Subject: RE: how many build.xml files and where should they go?
Date: Mon, 7 Apr 2003 13:54:51 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

I prefer many build.xml files throughout the source tree, with a single
build file at the parent to unite them all. Allows flexibility, without
cluttering the parent build script. You'll notice that most projects have
very similar patterns, that you can refactor out to a library of build
files, but most projects have at least one or two quirks about them (whether
they be ejb's, jsp precompilation, etc. etc.). I found that having them all
in a single script was very unwieldly and difficult to manage, and pushing
all of the customizations to each sub-directory has greatly helped for
management of the scripts. (However, I would make sure that you constantly
manage the distributed build scripts to ensure that you refactor as much as
possible).

d.


-----Original Message-----
From: Tim Singletary [mailto:tsingle@vetinsite.com]
Sent: Monday, April 07, 2003 1:44 PM
To: user@ant.apache.org
Subject: how many build.xml files and where should they go?


I haven't seen much discussion about this question, but there seem to
be two very different approaches to managing build.xml files.

One approach has a single build.xml at the top of the project tree.

The other approach has many build.xml files, one in each subdirectory
in the src tree.

Why should I choose one approach over the other?  Is either approach
generally preferred?

tim


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org