Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 10201 invoked by uid 2016); 13 Oct 1999 00:16:00 -0000 Delivered-To: apcore-jakarta-tomcat-cvs@apache.org Received: (qmail 10178 invoked from network); 13 Oct 1999 00:15:58 -0000 Received: from unknown (HELO mytown.us.world.net) (209.162.210.179) by taz.hyperreal.org with SMTP; 13 Oct 1999 00:15:58 -0000 Received: from mytownnet.com ([209.241.199.21]) by mytown.us.world.net (Netscape Messaging Server 3.01) with ESMTP id AAA23269; Tue, 12 Oct 1999 17:18:56 -0700 Message-ID: <3803CF21.3D51DD0B@mytownnet.com> Date: Tue, 12 Oct 1999 17:15:29 -0700 From: "Craig McClanahan" Organization: MyTown Network, Incorporated X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: stefano@hyperreal.org CC: jakarta-tomcat-cvs@apache.org Subject: Re: cvs commit: jakarta-tomcat build.xml README References: <19991012224308.106.qmail@hyperreal.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit stefano@hyperreal.org wrote: > stefano 99/10/12 15:43:08 > > Modified: . build.xml README > Log: > - Updated the README > - changed the "../build" to "./build" since it makes little sense to go back one directory > > These should not brake anything, but I'm not sure. We can go back if this is the case. > Prior to this change, the directory hierarchy looked like this: build/ build/tomcat/ <> jakarta-tomcat/ <> and after this change, it looks like this: jakarta-tomcat/ <> build/ tomcat/ <> It seems to me that, if we want this change, two additional things should happen: * Make the same change in each of the other projects, which probably do the same thing (I don't have the CVS tree in front of me to check). * Change "./build/tomcat/*" to "./build/*" everywhere to eliminate the redundant "tomcat" subdirectory underneath "build". On the other hand, I can see value in having the "build" hierarchy as it originally was -- the least of the benefits is that a "cvs commit" or "cvs update" at the jakarta-tomcat level does not have to waste time scanning the build directory. I would actually prefer the original approach for that reason. Craig