I succesfully staged the artifacts and was doing some final testing on them when I noticed that the contents of the jca/ra maven artifacts doesnt match the artifacts contained in the qpid-java-0.22.tar.gz file. One seems to have been created with Java 7 and the other with Java 6.
I don't think it would be a good idea to release two different versions of the same artifact, it seems like it would be best to rectify the discrepancy between them. The easiest way (short of a full rebuild) would be to extract the 3 jca+ra jars/rars from the qpid-java-0.22.tar.gz archive, drop them into the maven dir structure to overwrite the other files, and then re-sign them. Robbie On 28 May 2013 12:05, Justin Ross <[email protected]> wrote: > I've added the signature for the rar file now. > > On Mon, May 27, 2013 at 3:32 PM, Robbie Gemmell > <[email protected]> wrote: > > Ah...I forgot that one of the artifacts this time is actually a .rar > rather > > than .jar file. Can you sign it too please? > > > > I updated the release script accordingly: > > http://svn.apache.org/r1486699 > > > > Robbie > > > > On 27 May 2013 12:57, Justin Ross <[email protected]> wrote: > > > >> Thanks for catching that. I've added the jca maven artifacts to RC6. > >> > >> Justin > >> > >> On Sun, May 26, 2013 at 5:05 PM, Robbie Gemmell > >> <[email protected]> wrote: > >> > 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] > >> >> > >> >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
