maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WAGON-449) CLIENT not changed after setting PoolingHttpClientConnectionManager
Date Sun, 24 Jan 2016 07:12:39 GMT

    [ https://issues.apache.org/jira/browse/WAGON-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114226#comment-15114226
] 

Hudson commented on WAGON-449:
------------------------------

UNSTABLE: Integrated in maven-wagon #1302 (See [https://builds.apache.org/job/maven-wagon/1302/])
[WAGON-449] Use new connection manager when set (jeannikl: rev 4f42503a9aa6d6c03bfdf2562cb86eec194b70dd)
* wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagon.java
* pom.xml


> CLIENT not changed after setting PoolingHttpClientConnectionManager
> -------------------------------------------------------------------
>
>                 Key: WAGON-449
>                 URL: https://issues.apache.org/jira/browse/WAGON-449
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 2.8, 2.9, 2.10
>            Reporter: Jean Niklas L'orange
>            Assignee: Olivier Lamy (*$^¨%`£)
>             Fix For: 2.11
>
>
> The AbstractHttpClientWagon class statically creates both a PoolingHttpClientConnectionManager
and a client that uses said connection manager. This is fine, had it not been the case that
the client itself is a final field and is never updated.
> Thus, using {{setPoolingHttpClientConnectionManager}} has no effect as the client is
based on the PoolingHttpClientConnectionManager created at startup. This affects users that
e.g. may want to change the SSLContext to support self-signed certificates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message