Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 42717 invoked from network); 8 Nov 2006 16:05:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Nov 2006 16:05:11 -0000 Received: (qmail 38533 invoked by uid 500); 8 Nov 2006 16:05:20 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 38486 invoked by uid 500); 8 Nov 2006 16:05:19 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 38475 invoked by uid 99); 8 Nov 2006 16:05:19 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 08:05:19 -0800 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_IN_SORBS_WEB X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [209.86.89.69] (HELO elasmtp-mealy.atl.sa.earthlink.net) (209.86.89.69) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 08:05:05 -0800 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=m3mHw6Z/3i7MM0LPTU6AIM7GijPkz745EC+F4IWUcSbCQmYYSC/6KLOc1JCEGn9c; h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [129.33.49.251] (helo=[9.37.214.130]) by elasmtp-mealy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1Ghpuu-0007Pc-2x for dev@geronimo.apache.org; Wed, 08 Nov 2006 11:04:44 -0500 Message-ID: <45520019.6030409@earthlink.net> Date: Wed, 08 Nov 2006 11:04:41 -0500 From: Joe Bohn User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: Java EE 5.0 References: <1b5bfeb50611060912l6375ec22vcc8d4bef78f2e453@mail.gmail.com> <4550B8F8.7060408@Golux.Com> <1b5bfeb50611071350s2d0768bbof564d8b7ee0da80a@mail.gmail.com> <1A8BBCAA-C6D8-4FE8-9B30-7DFC3FD79FA1@yahoo.com> <75906B6C-926C-4E07-BDD7-FA532FB5ACB4@gmail.com> In-Reply-To: <75906B6C-926C-4E07-BDD7-FA532FB5ACB4@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec79ec63de83a4d26b69aa94eeec798bb663350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 129.33.49.251 X-Virus-Checked: Checked by ClamAV on apache.org Kevan Miller wrote: > 2) Develop in a sparse source tree. The source tree only contains the > new code that is being developed. The hope is that this reduces the > overhead of merging changes. However, it will also complicate the build > process -- it seems that Joe has been having problems building using > this technique. It isn't just a problem of building via a sparse tree (though it does make the build process more complex). I don't think it is feasible to manage a sparse tree for when "common components" that already live in trunk need to be updated as a result of some changes for a component in the sparse tree ... see my earlier response to David. If you really want to try the sparse tree approach then I think you need to move *all* configs out of trunk and into the sparse tree which will be disruptive to trunk (and hence 1.2). Joe