You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/02/16 20:14:00 UTC

[jira] [Closed] (MJAVADOC-483) Needs support for https.proxySet etc.

     [ https://issues.apache.org/jira/browse/MJAVADOC-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MJAVADOC-483.
-----------------------------------
    Resolution: Duplicate

[~ljnelson], this is being merged in to the other ticket. Please follow the discussion there and leave your comments.

> Needs support for https.proxySet etc.
> -------------------------------------
>
>                 Key: MJAVADOC-483
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-483
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 2.10.4
>            Reporter: Laird Nelson
>            Priority: Major
>
> I work at a ginormous company that has a proxy server.  I have an active {{<proxy>}} in my {{.m2/settings.xml}} for the {{http}} protocol.  The {{maven-javadoc-plugin}} picks this up fine.
> Weirdly, the {{javadoc}} invocation _also_ requires the {{https}} proxy to be set.  There is no way to accomplish this with the {{maven-javadoc-plugin}}.
> IMHO it should see if there is an active {{<proxy>}} element whose protocol is {{https}} as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)