Gordon Pettey commented on MNG-5950:

This is still a valid issue. I think it is a duplicate, though I cannot find 
the issue I had previously read that went more in depth. Basically, some 
getProxy method used by various plugins (e.g. m-javadoc-p) only returns the 
first active proxy from settings.xml, irrespective of protocol, so you can have 
either an HTTPS proxy or an HTTP proxy, but not both, and if you need Maven to 
connect to both protocols via proxy during a build, you simply can't. The most 
obvious way to experience this is of course with m-javadoc-p, with `<link>`s to 
both HTTP and HTTPS remotes. Only one or the other will be able to connect via 
proxy, depending on which is first in settings.xml.

> Only first active proxy considered
> ----------------------------------
>                 Key: MNG-5950
>                 URL: https://issues.apache.org/jira/browse/MNG-5950
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.5
>         Environment: windows 7 ,jdk 1.8
>            Reporter: Jiahongchao
> only http proxy or https proxy can be used at the same time,however,only one 
> proxy should be used for both http and https

This message was sent by Atlassian JIRA

Reply via email to