Ok, never mind! It looks like a eerie case of Apache community "telepathy" :-), because the VOTE succeeded a few hours ago and I was able to find the artifacts for 4.3.1 in Maven Central already.
Upgrade performed on our side, and it looks good so far. Thanks, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Tue, Oct 8, 2013 at 12:36 AM, Raul Kripalani <r...@evosent.com> wrote: > Hello fellow Apache folks, > > I'm writing on behalf of the Apache Camel project. We're eager to upgrade > to Apache HttpClient 4.3 for use by our camel-http4 component. In fact, we > already started the process [1] [2], but unfortunately we're faced with no > other option than to revert it due to HTTPCLIENT-1398 and HTTPCLIENT-1400, > as it happens that we have quite a large OSGi user base. > > What's more, this issue also affects several other Open Source libraries > such as: aws-java-sdk, CouchDB driver, Apache Solr Java driver, HBase > driver, and transitively, the associated Camel components: camel-aws, > camel-couchdb, camel-solr, camel-hbase. > > I can see that your VOTE to release version 4.3.1 is underway [3] and > looks good so far. > > Would you mind to quickly ping us as soon as the release is out and the > artifacts have been published to the Maven repos? We'd really appreciate > the nudge. I've CC'ed our dev@ list. > > [1] https://issues.apache.org/jira/browse/CAMEL-6806 > [2] https://issues.apache.org/jira/browse/CAMEL-6831 > [3] > http://mail-archives.apache.org/mod_mbox/hc-dev/201310.mbox/%3C1380830257.28583.42.camel%40ubuntu%3E > > Many thanks, > > *Raúl Kripalani* > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source > Integration specialist > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk >
