Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 41233 invoked by uid 500); 11 Jun 2001 20:05:58 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 41144 invoked from network); 11 Jun 2001 20:05:57 -0000 From: "Aaron Haspel" To: Subject: RE: hierarchial build.xml Date: Mon, 11 Jun 2001 16:04:38 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N -----Original Message----- From: Viraj Purang [mailto:viraj_purang@spincircuit.com] Sent: Tuesday, June 05, 2001 9:52 PM To: ant-user@jakarta.apache.org Subject: hierarchial build.xml HI, Is it possible to have the ant pick up the build.xml at a lower level by itself. I have a pretty unruly set of developers, who want to have the freedom to just add their valid build.xml file with the new code / directories they are checking in . It would be really nice if the upper most level build.xml file can pick this file automatically, rather than me having to specify the same as a part of the ANT tag. Thanks and Regards, Viraj Purang -----Original Message----- From: Diane Holt [mailto:holtdl@yahoo.com] Sent: Thursday, May 03, 2001 1:49 PM To: ant-user@jakarta.apache.org Subject: Re: Basic question Javac ... (it is long !!!) Whether to have build-files for each of your modules is a design decision. If you go with just a single build-file at the top of the tree, and your build process is complicated, then having everything in one file can tend to get a bit unwieldy. On the other hand, if your process is fairly straightforward, having a single build-file may be easier to maintain. You can have targets in your build-file for each of your modules (assuming you want to be able to build them individually) and, say, an "all" target that either "depends" on all the targets needed to build everything, or, if you need to override property values, does 's to those targets that need that. If you go with individual build-files, you can still have an "all" target in your top-level build-file, but it would do 's to those other build-files instead. One advantage of having individual build-files is that you can have a default target for each of those, so that when you're doing development, and you're down in some module sub-directory, you can just use 'ant' to recompile (assuming your default target is to do compiles) rather than having to specify the module's target in the top-level file. As an example of a single top-level build-file, you can look at the build.xml file Ant itself (but be prepared -- it's pretty huge :) As an example of a build-file that has sub-project build-files, see the build.xml for Tomcat-4.0 at: http://jakarta.apache.org/cvsweb/index.cgi/jakarta-tomcat-4.0/build.xml?rev= 1.21&content-type=text/vnd.viewcvs-markup Hope this helps, Diane --- Viraj Purang wrote: > Hi, > I am new to the ANT scene, so a silly question. > I have multiple modules in CVS each having its own src directory > > > CVS Structure for module ... > --------------------------------------- > > > properties > com > > > needed> > > > images > > public_html > > > > > src > javabeans > com > > > > > > > servlets > com > > > > > > SO do I need to have seperate hierarchy of build.xml files at each > directory level or only one at the topmost level to build. > In case I need a hierarchy ...how do I code that ? PLease POint me some > examples if you can !!! > > Regards, > Viraj Purang > ===== (holtdl@yahoo.com) __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/