Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 2510 invoked from network); 27 Jun 2006 07:42:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jun 2006 07:42:46 -0000 Received: (qmail 47972 invoked by uid 500); 27 Jun 2006 07:42:42 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 47933 invoked by uid 500); 27 Jun 2006 07:42:42 -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 47922 invoked by uid 99); 27 Jun 2006 07:42:42 -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 00:42:42 -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 jason.dillon@gmail.com designates 66.249.82.197 as permitted sender) Received: from [66.249.82.197] (HELO wx-out-0102.google.com) (66.249.82.197) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 00:42:41 -0700 Received: by wx-out-0102.google.com with SMTP id h30so960849wxd for ; Tue, 27 Jun 2006 00:42:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:subject:date:to:x-mailer:from:sender; b=OcpHbPHIMdCY4rS0nr0tDlHGErPtc4oW42vU04AkcpC08xdkF4SJ4gAKsyV1mO3gB/OOH27jCufQXJ5Whfy8h8z62rjcxLL5EA0DHStyEIarJx3ZjQJdOaiq4/Z4mvkOStxKh3dkeetyBMCS2V4wdlU4GyLV4lzVmd4mA0wW4dg= Received: by 10.70.16.4 with SMTP id 4mr9852320wxp; Tue, 27 Jun 2006 00:42:20 -0700 (PDT) Received: from ?10.0.1.5? ( [67.180.143.96]) by mx.gmail.com with ESMTP id h10sm5120275wxd.2006.06.27.00.42.20; Tue, 27 Jun 2006 00:42:20 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <44A0DF2C.7010204@gmail.com> 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> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Subject: Re: Lets start moving to m2 Date: Tue, 27 Jun 2006 00:42:11 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.750) From: Jason Dillon Sender: Jason Dillon X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I agree that trunk should always be buildable... though its been months since I've been able to build from the trunk :-P --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 >> >> >