Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 10826 invoked from network); 8 Jun 2002 00:05:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Jun 2002 00:05:29 -0000 Received: (qmail 267 invoked by uid 97); 8 Jun 2002 00:05:24 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 136 invoked by uid 97); 8 Jun 2002 00:05:24 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 29945 invoked by uid 98); 8 Jun 2002 00:05:22 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Fri, 7 Jun 2002 17:05:06 -0700 (PDT) From: costinm@covalent.net X-X-Sender: costin@costinm.sfo.covalent.net To: Tomcat Developers List Subject: Re: PROPOSAL: build directories In-Reply-To: <019801c20e7b$e6755290$6501a8c0@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 7 Jun 2002, Remy Maucherat wrote: > I agree this is not perfect, but IMO it is a lot less risky that ../build. I > could indeed maintain completely separate environments, but this is not very > convinient or efficient (at least for me). Note that the current system > doesn't prevent you from doing that (but the one you propose would require > you to do so). The problem is that I loose track of all the dozens of projects, each with different conventions and locations. By 'clean build' I meant building all the projects from their sources, to make sure all things are in sync. My conclusion so far - it's impossible to do so, there are far too many inderdependencies and chicken-egg problems. For 4.x we do build in 7 different places: - jakarta-tomcat-4.0/catalina/build - j-t/jasper/build - j-t-jasper/jasper2/build - j-t-c/util/build - j-t-c/jk/build - j-t-c/coyote/build - j-t-c/http11/build To that you can add about 10 different build directories for jakarta-commons ( 3-4 ), log4j, mx4j, etc. Of course, it's simpler with checked-in binaries, but if you want to debug a cross-project problem it's hell. Jars are scatered in at least 20 directories. Can you do a full build of tomcat ( including all dependent jars that are open source ) ? Costin > > > At least at my level of knowledge about jakarta and tomcat - I find > > it close to impossible to have a clean build ( i.e. from sources ). > > You'll notice that 'ant clean' in TC 4 clears all the Tomcat source > dependencies, to avoid that. > > Remy > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: