Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Potential for errors with p2 update and http client version

I have not heard of any other reporters of this.   I got it hit with it again recently and wanted to make others aware while testing M3.  If your installation contains multiple versions of the apache http client then you could be hit by

My installation of jgit happens to pull in an older version of apache http client and I get hit with the following exception when trying to update with p2.

java.lang.NoSuchMethodError: org.apache.http.impl.client.DefaultHttpClient.execute(Lorg/apache/http/client/methods/HttpUriRequest;Lorg/apache/http/protocol/HttpContext;)Lorg/apache/http/client/methods/CloseableHttpResponse;
        at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.performConnect(
        at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.access$0(
        at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer$1.performFileTransfer(

The only work around I have found is to bring up the osgi> console and manually refresh the org.eclipse.ecf.provider.filetransfer.httpclient4 bundle:

osgi> refresh org.eclipse.ecf.provider.filetransfer.httpclient4

That allows ecf to be rewired to the latest version of apache.  I suspect I am hitting this because I do build to build upgrades which has been updating the latest version of apache http client recently.  This ends up causing ecf to be re-resolved and wires to the pre-resolved older version still left around.


Back to the top