Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 83868 invoked from network); 17 Aug 2005 17:57:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Aug 2005 17:57:06 -0000 Received: (qmail 19091 invoked by uid 500); 17 Aug 2005 17:57:02 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 19052 invoked by uid 500); 17 Aug 2005 17:57:02 -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 19039 invoked by uid 99); 17 Aug 2005 17:57:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2005 10:57:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [72.10.34.3] (HELO ss53.shared.server-system.net) (72.10.34.3) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2005 10:57:21 -0700 Received: from [127.0.0.1] (lgb-cust-216.70.135.24.mpowercom.net [216.70.135.24] (may be forged)) (authenticated bits=0) by ss53.shared.server-system.net (8.12.11/8.12.11) with ESMTP id j7HHuwlc018463 for ; Wed, 17 Aug 2005 10:56:59 -0700 Message-ID: <43037A68.8050702@toolazydogs.com> Date: Wed, 17 Aug 2005 10:56:56 -0700 From: "Alan D. Cabrera" Organization: Mergere User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2) References: <1887168797.1124280235427.JavaMail.jira@ajax.apache.org> <2584B635-0C8D-4C75-B44E-01FEC150DCF9@apache.org> <43036717.2010303@toolazydogs.com> <430368F4.1040804@toolazydogs.com> <274EDEB2-D912-40A1-A5A1-2E22BBFB8839@apache.org> In-Reply-To: <274EDEB2-D912-40A1-A5A1-2E22BBFB8839@apache.org> 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 I think that some work can be done investigating where the jelly lies. We can then add sub-tasks to track their conversion. All of this can be done w/out interfering with the M5 release. Regards, Alan Geir Magnusson Jr. wrote, On 8/17/2005 9:54 AM: > Thx. > > I think we should consider choosing appropriate timing - it sounds > like a big effort, and how does this fit into what we want to do w/ > M5, 1.0, etc I was going to suggest voting on even doing this, but I > can't imagine that at *some* point in the future, we don't want to be > on M2, so we will go there eventually. it's just a matter of when... > > geir > > On Aug 17, 2005, at 12:42 PM, Alan D. Cabrera wrote: > > >> To be a little more specific, maven 1 and maven 2 can both work with >> maven 2 POMs. It's our non-standard jelly code that impedes our >> conversion. We need to enumerate where that code is, determine if >> there is an M2 replacement for it, it not decide if we need it and >> if we do, make a plug in or convert the code. >> It is my understanding that much of the jelly code is optimizations, >> e.g. don't run tests if they've already been run. The maven team is >> happy to make such optimizations a priority to include in M2. >> >> After the conversion, I hope that we have no more jelly. >> >> >> Regards, >> Alan >> >> Alan D. Cabrera wrote, On 8/17/2005 9:34 AM: >> >> >> >>> Normally, yes. Unfortunately there is a lot of jelly code out there. >>> >>> Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM: >>> >>> >>> >>>> Is it backwards compatible? >>>> >>>> IOW, can people that use M1 also still work? >>>> >>>> >>> >>> >>> >> >> >> >> >