[ http://jira.codehaus.org/browse/MNG-1829?page=all ]
Lukas Theussl moved MPJAVADOC-67 to MNG-1829: --------------------------------------------- Complexity: Intermediate Workflow: Maven (was: jira) Key: MNG-1829 (was: MPJAVADOC-67) Project: Maven 2 (was: maven-javadoc-plugin) > plugin should honor proxy settings > ---------------------------------- > > Key: MNG-1829 > URL: http://jira.codehaus.org/browse/MNG-1829 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Environment: tested on Linux/Windows > Reporter: Dirk Olmes > Priority: Minor > > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]