I just tried staging the maven artifacts on the ASF Nexus instance so they were ready for the release vote closing, and while doing so found that the maven artifacts for the JCA module are not present. They are being built but not copied into the final artifact area by the release script. I made a change on trunk that should fix that: http://svn.apache.org/r1486474
I don't think the script change necessarily warrants another RC as it is really just a convenience, and the actual source is unchanged...but I would like to see the missing artifacts released (particularly given people asked for them last year and they missed the cut for the previous release). If you still have the build output from preparing the RC, rather than do a full rebuild you could simply sign the jar and pom files under java/jca/release/maven as would have happened if the release script had copied them and then upload the contents to the relevant spot. Robbie On 26 May 2013 11:31, Justin Ross <[email protected]> wrote: > RC6 from revision 1486100: > > http://people.apache.org/~jross/qpid-0.22-rc6/ > http://people.apache.org/~jross/qpid-0.22-rc6-testing.txt > > This release candidate is signed. The bits in RC6, if approved for > release, will be the GA bits. > > I withdrew the last vote, for RC5, and I'm starting a new vote today. > > Thanks, > Justin > > --- > 0.22 release page: https://cwiki.apache.org/qpid/022-release.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
