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

ASF GitHub Bot commented on WAGON-449:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/maven-wagon/pull/21


> 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)

Reply via email to