[
https://issues.apache.org/jira/browse/MJAVADOC-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957378#comment-17957378
]
Olivier Lamy commented on MJAVADOC-3:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[olamy/maven-javadoc-plugin#396|https://github.com/olamy/maven-javadoc-plugin/issues/396].
> plugin should honor proxy settings
> ----------------------------------
>
> Key: MJAVADOC-3
> URL: https://issues.apache.org/jira/browse/MJAVADOC-3
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Environment: tested on Linux/Windows
> Reporter: Dirk Olmes
> Assignee: Maria Odea B. Ching
> Priority: Minor
> Fix For: 2.0
>
> Attachments: MJAVADOC-3-maven-javadoc-plugin.patch,
> MJAVADOC-3-maven-javadoc-plugin.patch
>
> Original Estimate: 3.5h
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The maven2 plugin should honor the proxy settings. When specifying the <link>
> option, the forked javadoc process always tries to fetch the package-list
> directly. This fails on corporate networks, where all web access has to go
> through a proxy.
> I've tried to specify a proxy by using the <additionalparam> option but this
> does not work because all parameters for the javadoc process are written to
> an options file, which is passed to the forked javadoc process. By the time
> the javadoc process gets to see the arguments, it is already running so all
> VM parameters (-J-Dhttp.proxyHost...) cause errors.
> The most seamless integration would be to pass whatever proxy is configured
> to the forked javadoc process. Configuration options for specifying the proxy
> for the javadoc-plugin would be acceptable, too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
