Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 82450 invoked from network); 23 Sep 2006 16:16:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Sep 2006 16:16:09 -0000 Received: (qmail 33136 invoked by uid 500); 23 Sep 2006 16:16:08 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 32775 invoked by uid 500); 23 Sep 2006 16:16:06 -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 32764 invoked by uid 99); 23 Sep 2006 16:16:06 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Sep 2006 09:16:06 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=david_jencks@yahoo.com; domainkeys=good Authentication-Results: idunn.apache.osuosl.org smtp.mail=david_jencks@yahoo.com; spf=permerror X-ASF-Spam-Status: No, hits=4.8 required=5.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,HTML_MESSAGE Received-SPF: error (idunn.apache.osuosl.org: domain yahoo.com from 68.142.206.236 cause and error) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [68.142.206.236] ([68.142.206.236:44117] helo=smtp103.plus.mail.mud.yahoo.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 05/3F-27820-2CD55154 for ; Sat, 23 Sep 2006 09:16:04 -0700 Received: (qmail 24102 invoked from network); 23 Sep 2006 16:15:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:From:Subject:Date:To:X-Mailer; b=I0a4bBKI1jt6b7X/UZ6uDL6GObV54OHd49PkGB2ApJRl/Y9TVHyaoSfwC5v7fe1c+DvGMG6z+SLycq0gSUDoYH0HhYZrsd5NuUtpaGHH1Fjsq5tAcZuT2G5GdWjJYtqODNBY1ysAixLn3JBfdFus3GCi+PnWKjY5uPsvq7EFNzY= ; Received: from unknown (HELO ?10.11.55.38?) (david?jencks@63.105.20.225 with plain) by smtp103.plus.mail.mud.yahoo.com with SMTP; 23 Sep 2006 16:15:59 -0000 Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <22d56c4d0609230615h795a0b48i1549ecdece9b6bac@mail.gmail.com> References: <451479E9.3080505@joyfulnoisewebdesign.com> <1b5bfeb50609230543y7b7e91a9m22bf339dc606f4aa@mail.gmail.com> <22d56c4d0609230615h795a0b48i1549ecdece9b6bac@mail.gmail.com> Content-Type: multipart/alternative; boundary=Apple-Mail-1-332332203 Message-Id: <776DA7C6-4536-4624-A2FC-D38AE237D2B0@yahoo.com> From: David Jencks Subject: Re: maven.xml is pointing to the wrong version of OpenEJB in branches/1.1 Date: Sat, 23 Sep 2006 09:15:58 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.749.3) X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Apple-Mail-1-332332203 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 23, 2006, at 6:15 AM, Vamsavardhana Reddy wrote: > Is branches/1.1 frozen? I thought it is only tags/* that are frozen. no branches/x.x are frozen: they can be fixed all tags/* are frozen and they cannot be changed This problem suggests to me that m:co and similar goals have no place in a build script and if we keep the facility they need to go in something that isn't a build script. I also wonder if we should be zipping up the maven repo used for a released build and stashing it in the svn tag for the release. e.g start with empty m repo, build g, remove all g artifacts from the repo, and zip it up. Checking that g then builds offline is probably a good idea too. thanks david jencks > > Vamsi > > On 9/23/06, Jacek Laskowski wrote: > On 9/23/06, Jay D. McHugh wrote: > > Hello all. > > > > I didn't figure this was worth a JIRA. > > It still is ;-) > > > The maven.xml file in branches/1.1 is still pointing to codehaus > for its > > openejb checkout (and an older version too). > > > > Here is a patch (my first patch for Geronimo!) > > Thanks Yay for having caught it! > > I don't know if I can patch the branch after it's released? I mean, to > me the branch is frozen. OTOH, it's unreasonable to create another > branch just to patch 1.1 - it doesn't require a separate release. I'd > like to hear others' opinion before proceeding. > > Unless I hear an objection, I'll patch it after 48h have passed. > > Jacek > > -- > Jacek Laskowski > http://www.laskowski.net.pl > --Apple-Mail-1-332332203 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
On Sep 23, 2006, = at 6:15 AM, Vamsavardhana Reddy wrote:

Is = branches/1.1 frozen?=A0 I thought it is only tags/* that are = frozen.

no branches/x.x are frozen: they = can be fixed=A0

all tags/* are frozen and = they cannot be changed

This problem suggests to me = that m:co and similar goals have no place in a build script and if we = keep the facility they need to go in something that isn't a build = script.

I = also wonder if we should be zipping up the maven repo used for a = released build and stashing it in the svn tag for the release.=A0 e.g = start with empty m repo, build g, remove all g artifacts from the repo, = and zip it up.=A0 Checking that g then builds offline is probably a good = idea too.

thanks
david = jencks


= --Apple-Mail-1-332332203--