Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (hermes.apache.org: domain of david.blevins@visi.com
 designates 208.42.156.2 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <FB350567-4EB0-461F-944D-66A35EDE7C12@gmail.com>
References: <44ADD549.7050006@apache.org>
 <FB350567-4EB0-461F-944D-66A35EDE7C12@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F66CD375-A57B-4C85-881A-2EC7181468FD@visi.com>
Content-Transfer-Encoding: 7bit
From: David Blevins <david.blevins@visi.com>
Subject: Re: Tag 1.1 issue?
Date: Fri, 7 Jul 2006 08:34:43 -0700
To: dev@geronimo.apache.org


On Jul 7, 2006, at 6:32 AM, Kevan Miller wrote:

>
> On Jul 6, 2006, at 11:30 PM, Jeff Genender wrote:
>
>> I tried to build the v1.1 of Geronimo tag and I noticed that when  
>> I went
>> to do a m:co of openejb, it is giving me the openejb branch  
>> instead of
>> the 2.1 tag.  Sure enough, upon perusal of the tagged root maven.xml,
>> its pulling the openejb branch and not the tag.
>>
>> I am assuming this is an oversight and it should pull the tag orf
>> openejb, not the branch.  Do we need this fixed so we can do a  
>> build of
>> our svn tagged 1.1?
>
> Yes, I noticed this yesterday, also. The build works if you don't  
> run m:co (the openejb 2.1 dependencies). So, I don't think we need  
> to rush to fix this. Instead we can wait to fix in the normal 1.1.1  
> release cycle, which I think should be soon (in July).
>
> Clearly something that needs to be in a release process checklist.

At release time is one of the rare moments where we don't have a  
snapshot dependency on OpenEJB.  Why wouldn't we just disable the m:co?

-David