The maven artifacts folder doesnt seem to contain everything I expected it should. Only the client and common artifacts are present, whereas Andrew had previously added additional artifacts which are mentioned in the ivy.xml file used for upload and the release.sh script. Was an old copy of the release script possibly used to generate the build?
Everything else I tested (Java broker, client, management artifacts) seemed fine and I was on course to just vote positively until I noticed that. Do you happen to still have the build folder used to generate the artifacts to see if they were actually built? Either they still exist and we use them, or we decide to rebuild them, or we just modify the ivy.xml file and upload the existing artifacts without them. Thoughts? Robbie On 12 December 2011 14:58, Justin Ross <[email protected]> wrote: > Hello, everyone. There have been no new changes on the release branch since > our proposed final RC, available here: > > http://people.apache.org/~jross/qpid-0.14/ > > If you favor releasing this distribution as Qpid 0.14, vote +1. If instead > you think there are problems that should prevent this distribution from > being released, vote -1. > > I'd like to complete the vote by Thursday so I can push the release Friday, > provided we vote in favor. > > Thanks, everyone, for all your help getting the release out. > > Justin > > --- > 0.14 release page: https://cwiki.apache.org/qpid/014-release.html > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
