Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 98227 invoked from network); 27 Jun 2006 11:38:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jun 2006 11:38:52 -0000 Received: (qmail 40527 invoked by uid 500); 27 Jun 2006 11:38:47 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 40481 invoked by uid 500); 27 Jun 2006 11:38:47 -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 40470 invoked by uid 99); 27 Jun 2006 11:38:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 04:38:46 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jrsisson@gmail.com designates 66.249.82.202 as permitted sender) Received: from [66.249.82.202] (HELO wx-out-0102.google.com) (66.249.82.202) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 04:38:45 -0700 Received: by wx-out-0102.google.com with SMTP id h30so982494wxd for ; Tue, 27 Jun 2006 04:38:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=m4acbfdFFUZjzhrY8WOm8kJOKYiiCSxb9FP6rCuu8JA9NqW10HopNNGI1cKJReCGti/z+FGbOK/CGU4VMfLfI0OqhOoFtEJZENfU83vYuF5Znt2ckOvd1Slv00ierB0CV3Jr7HlsVaCRPvz2GHhpLF6navdSAUq7fVvYcVD8doQ= Received: by 10.70.71.4 with SMTP id t4mr10200752wxa; Tue, 27 Jun 2006 04:38:24 -0700 (PDT) Received: from ?192.168.0.20? ( [59.167.41.238]) by mx.gmail.com with ESMTP id i37sm6454823wxd.2006.06.27.04.38.21; Tue, 27 Jun 2006 04:38:23 -0700 (PDT) Message-ID: <44A1188C.8080303@gmail.com> Date: Tue, 27 Jun 2006 21:37:48 +1000 From: John Sisson User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: Lets start moving to m2 References: <5D194F2A-135A-4980-9D91-D92D2E62ADF1@yahoo.com> <1b5bfeb50606261105o4afaa14cvbdce01a6b7af0371@mail.gmail.com> <0C99DD37-4C45-404A-996F-EA83C72431BF@yahoo.com> <1b5bfeb50606261256x74a9d06dxf6a0220459bb858a@mail.gmail.com> <44A0B1C0.3040603@toolazydogs.com> <45E439DA-EE42-4774-B7FB-B45D6458D044@planet57.com> <44A0DF2C.7010204@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jason Dillon wrote: > I agree that trunk should always be buildable... though its been > months since I've been able to build from the trunk :-P > I assume you mean you haven't been able to build using m2, not m1. m1 builds work fine for me. John > --jason > > > On Jun 27, 2006, at 12:33 AM, John Sisson wrote: > >> I don't think we should be removing files until we have a 100% >> functional m2 build. The trunk should always be buildable. >> If the M2 build isn't going to be straightforward we should have some >> information in something like the README.txt file documenting how the >> build should be executed. >> >> John >> >> Jason Dillon wrote: >>> I think that removing the m1 files is a good idea, as it will help >>> force us to get m2 to build... which really should not take that >>> long to get functional 100% of the time. >>> >>> --jason >>> >>> >>> On Jun 26, 2006, at 9:19 PM, Alan D. Cabrera wrote: >>> >>>> Jacek Laskowski wrote: >>>>> On 6/26/06, David Jencks wrote: >>>>> >>>>>> I'm suggesting that we declare the m1 build obsolete and remove it, >>>>>> except possibly for the assembly step and perhaps modules where the >>>>>> tests do not run under m2. >>>>> >>>>> Well, don't get it annoying, but I still don't understand it. Let's >>>>> pretend we've named the m1 build obsolete, what's next? Shall we call >>>>> a vote? If it passes, what would be the next steps? If you removed >>>>> the >>>>> top-level build.xml I'd know what it'd mean, but now I don't get it. >>>> >>>> Yes, we call a vote then remove the project.xml/project.properties >>>> files. build.xml is for Ant; I don't think we use that. >>>> >>>> >>>> Regards, >>>> Alan >>> >>> >> > >