I think leaving the tag as is will be fine, having the correct info in the pom is important.
On 27 April 2010 17:49, David Jencks <david_jen...@yahoo.com> wrote: > > On Apr 27, 2010, at 1:21 AM, Dejan Bosanac wrote: > > > +1 > > > > BTW we don't need to redo a release to change svn tag. Let's do it > manually > > with "svn mv". It would be good to have apache pom 7 and everything fixed > > for the 5.4 release though. > > I thought of svn mv, but the svn info in the released pom will then be > wrong. Is that OK? > > I'll try to get to the pom updates later this week or next week.... please > announce a couple days before 5.4 in case I get distracted :-) > > thanks! > david jencks > > > > > Cheers > > -- > > Dejan Bosanac - http://twitter.com/dejanb > > > > Open Source Integration - http://fusesource.com/ > > ActiveMQ in Action - http://www.manning.com/snyder/ > > Blog - http://www.nighttale.net > > > > > > On Tue, Apr 27, 2010 at 10:14 AM, Rob Davies <rajdav...@gmail.com> > wrote: > > > >> +1 > >> On 27 Apr 2010, at 00:04, David Jencks wrote: > >> > >>> Hi, > >>> > >>> I've staged a release candidate for ActiveMQ 5.3.2. The main driver > for > >> this is to get the osgi version range fixes into a release usable by the > >> upcoming geronimo 3.0 milestone. > >>> > >>> The changes since the recent 5.3.1: > >>> > >>> merging 881433 - jaxb plugin problem > >>> changing activemq.version to match project version > >>> AMQ-2501 Modify version range for camel imports > >>> AMQ-2637 port osgi version range fixes from trunk > >>> AMQ-2700 - code disclosure vunl > >>> AMQ-2675 - web console topic form > >>> > >>> The staging repo is here: > >>> > >>> > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-022/ > >>> > >>> The svn tag is here: > >>> > >>> https://svn.apache.org/repos/asf/activemq/tags/activemq-parent-5.3.2 > >>> > >>> This seems to be a different name format than the other tags. If > people > >> want me to redo the release to fix this I will probably want to update > the > >> build a little more such as using apache 7 parent pom and making the > release > >> plugin defaults work. > >>> > >>> Please vote > >>> > >>> +1 Promote staging repo as amq 5.3.2 > >>> -1 Drop staging repo and tag, try again (please provide specific > >> comments) > >>> > >>> Many thanks > >>> > >>> david jencks > >>> > >> > >> > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
