I am working in a Maven project which declares the following meen denigrations
& Lt; Properties & gt; & Lt; Httpclient.version & gt; 4.2.5 & LT; /httpclient.version> & Lt; CF-Client-lib.version & gt; 1.1.1 & LT; /cf-client-lib.version> .... & lt; / Properties & gt; & Lt; Dependency & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.httpcomponents & lt; / Group & gt; & Lt; ArtifactId & gt; Httpclient & lt; / ArtifactId> & Lt; Version & gt; 4.2.5 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.cloudfoundry & lt; / Group & gt; & Lt; ArtifactId & gt; Cloudfoundry-client-lb & lt; / ArtifactId> & Lt; Version & gt; 1.1.1 & lt; / Edition & gt; & Lt; / Dependencies & gt; ... & lt; Blocking & gt;
The problem is that version 4.3.6 of cloudfoundry-client-lib
httpclient
uses. I have read about this problem in fact, I get a post about it (using the same example).
I checked this problem using the mvn dependence: tree-darbos
, as indicated:
[INFO ] + - org.cloudfoundry: cloudfoundry-client-lib: jar: 1.1.1: compile: compilation - omitted for conflict with 4.0.5.RELEASE) [INFO] | + - (org.apache.httpcomponents: httpclient: jar: 4.2.5: compiled version - managed from 4.3.6; left for duplicate) [INFO] + - org.apache.httpcomponents: httpclient: jar: 4.2 .5: compilation [INFO] | + - (org.apache.httpcomponents: httpcore: jar: 4.2.5: compile)
I have read about the possible solutions described above, but I think I should give my project Update is the latest library version ( 4.3.6
) and (then, I could use). However, can I find an easy and temporary solution to continue the current development?
No comments:
Post a Comment