[ http://jira.codehaus.org/browse/MJAVADOC-3?page=comments#action_60889 ]
Vincent Siveton commented on MJAVADOC-3: ---------------------------------------- I think a better approach could be to use user system settings defined by maven-settings. WDYT? > plugin should honor proxy settings > ---------------------------------- > > Key: MJAVADOC-3 > URL: http://jira.codehaus.org/browse/MJAVADOC-3 > Project: Maven 2.x Javadoc Plugin > Type: Bug > Environment: tested on Linux/Windows > Reporter: Dirk Olmes > Assignee: Maria Odea Ching > Priority: Minor > Fix For: 2.0-beta-4 > Attachments: MJAVADOC-3-maven-javadoc-plugin.patch > > Original Estimate: 3 hours, 30 minutes > Time Spent: 3 hours, 30 minutes > Remaining: 0 minutes > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
