maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Ramirez (JIRA)" <>
Subject [jira] Closed: (MJAVADOC-3) plugin should honor proxy settings
Date Tue, 14 Mar 2006 06:19:30 GMT
     [ ]
Allan Ramirez closed MJAVADOC-3:

    Resolution: Fixed

Applied patch. 

> plugin should honor proxy settings
> ----------------------------------
>          Key: MJAVADOC-3
>          URL:
>      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, MJAVADOC-3-maven-javadoc-plugin.patch
> Original Estimate: 3 hours, 30 minutes
>        Time Spent: 4 hours
>         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:
For more information on JIRA, see:

View raw message