[
https://issues.apache.org/jira/browse/MJAVADOC-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020149#comment-16020149
]
Michael Osipov commented on MJAVADOC-483:
-----------------------------------------
I have encountered this issue several times at work too. This is a general
problem not limited to this plugin. The entire {{settings.xml}} stuff is poorly
designed from these days POV. A proper solution for this would be to modify the
settings stuff to more flexible.
> 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
>
> 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
(v6.3.15#6346)
