Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer;
  b=UaLJL5pgParTO+Jqj7Und0jFpJehqPoNUSq/OBbf4dL7FyxBvxqNF4BtGnD9ugupx3DwAwnySPon4NLH4tUcsXdy01Xu96/sXDWZQ3GyJm6puJib/9oMJ0xji7EUitnyMc1veUMM4Umwc+ZbzihDJj5AntB4ThmviiblsHMrmdY=
  ;
Message-Id: <66AC23C9-58E6-4416-8FE0-00399FADB672@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: dev@geronimo.apache.org
In-Reply-To: <4ACA44CE.6010601@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: [Fwd: Re: [VOTE] Release geronimo-jpa_2.0_spec-1.0-PFD2 and
 geronimo-validation_1.0_spec-1.0-CR5 for OpenJPA (2nd try)]
Date: Mon, 5 Oct 2009 12:36:26 -0700
References: <4ACA3F71.5000406@apache.org> <4ACA44CE.6010601@apache.org>


On Oct 5, 2009, at 12:11 PM, Donald Woods wrote:

> The release plugin failed to create the tag for me, even when I  
> followed the instructions at [1] and tried different maven levels.
>
> [1] http://maven.apache.org/developers/release/releasing.html

what svn version do you have locally?  There were some svn 1.5 clients  
that could not seem to execute some really simple commands.  IIRC  
there was an svn up you could run after the failure to work around  
these.  I haven't had this problem with  the svn 1.6.5 client I'm  
using now.

thanks
david jencks

>
> So, I created a branch instead and used "mvn deploy" to publish the  
> artifacts to the Nexus repo, which automatically created a staging  
> site for me.  Not sure if it was the strange "1.0-PFD2" and "1.0- 
> CR5" version naming that caused the release plugin to barf, as even  
> with running maven with "-e -X" there was no details to why the tag  
> commit was failing.
>
>
> -Donald
>
>
> Donald Woods wrote:
>> Forwarding to Geronimo thread....
>> -------- Original Message --------
>> Subject: Re: [VOTE] Release geronimo-jpa_2.0_spec-1.0-PFD2 and  
>> geronimo-validation_1.0_spec-1.0-CR5 for OpenJPA (2nd try)
>> Date: Mon, 5 Oct 2009 11:30:51 -0700
>> From: David Jencks <david_jencks@yahoo.com>
>> Reply-To: dev@openjpa.apache.org
>> To: dev@openjpa.apache.org
>> References: <4AC4CB8F.9040700@apache.org>
>> +1
>> source archives build OK for me, legal stuff looks ok.  I wish the
>> LICENSE files were more correct but it's not enough to redo the vote.
>> I'm curious how you generated this if it doesn't already have an svn
>> tag.... IMO all releases should be done with the release plugin which
>> I would expect would generate the tags directly.
>> thanks
>> david jencks
>> On Oct 1, 2009, at 8:32 AM, Donald Woods wrote:
>>> OpenJPA would like to release a 2.0.0 Milestone 3 release next  
>>> week  based on the JPA 2.0 PFD2 spec level. To do this, they need  
>>> released  versions of the Geronimo JPA2 and Bean Validation spec  
>>> APIs.
>>>
>>> This is the second vote for the geronimo-jpa_2.0_spec-1.0-PFD2  
>>> and  geronimo-validation_1.0_spec-1.0-CR5 spec apis, which  
>>> required  NOTICE updates to conform to the new ASF/Sun agreement  
>>> for releasing  early access specs.  A new geronimo-staging-017 has  
>>> been created  with the updated artifacts.
>>>
>>> geronimo-jpa_2.0_spec-1.0-PFD2
>>> source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-jpa_2.0_spec-1.0-PFD2
>>> svn revision:820677
>>> artifacts:https://repository.apache.org/content/repositories/geronimo-staging-017/
>>>
>>> geronimo-validation_1.0_spec-1.0-CR5
>>> source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-validation_1.0_spec-1.0-CR5
>>> svn revision:820678
>>> artifacts:https://repository.apache.org/content/repositories/geronimo-staging-017/
>>>
>>> Both of the above passed rat:check and the ianal plugin.  The jar   
>>> and source artifacts include the License and Notice files.
>>>
>>> The branches will be moved to tags and the staging artifacts   
>>> promoted to the release repo if the vote passes.
>>>
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1 (and reason why)
>>>
>>>
>>> Thanks,
>>> Donald