Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 33820 invoked from network); 7 Apr 2003 17:44:44 -0000 Received: from mail11b.verio-web.com (161.58.148.49) by daedalus.apache.org with SMTP; 7 Apr 2003 17:44:44 -0000 Received: from www.vetinsite.com (198.173.230.79) by mail11b.verio-web.com (RS ver 1.0.78vs) with SMTP id 0285817472 for ; Mon, 7 Apr 2003 13:44:32 -0400 (EDT) From: Tim Singletary MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16017.47352.334967.472974@macaw.hq.vetinsite.com> Date: Mon, 7 Apr 2003 13:44:24 -0400 To: user@ant.apache.org Subject: how many build.xml files and where should they go? X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-Loop-Detect: 1 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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