[ 
http://jira.codehaus.org/browse/MJAVADOC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Siveton closed MJAVADOC-252.
------------------------------------

    Resolution: Fixed

Maxime confirmed me the resolution in private

> javadoc link : nonproxyhosts not used
> -------------------------------------
>
>                 Key: MJAVADOC-252
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-252
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6
>         Environment: maven-2.0.10
> jdk 1.6_014
>            Reporter: Maxime Gréau
>            Assignee: Vincent Siveton
>            Priority: Minor
>             Fix For: 2.6.1
>
>         Attachments: link_nonproxy_2.0.10.patch, link_nonproxy_2.2.0.patch
>
>
> - Prerequisite : 
> --------------------
> - web access via http proxy
> - javadoc-plugin configuration with <detectLinks>true</detectLinks>
> - $MVN_HOME/conf/settings.xml with configuration above ( internal-host is 
> host to access the internal javadoc web sites )
>  <proxies>
>     <proxy>
>       <active>true</active>
>       <protocol>http</protocol>
>       <host>myproxyhost</host>
>       <port>myproxyport</port>
>       <nonProxyHosts>internal-host</nonProxyHosts>
>     </proxy>
> </proxies>
> Launch the mvn site-deploy command. 
> If you have a dependency with an internal javadoc web site, the plugin tried 
> to link this javadoc with the http proxy and logged:
> "Error fetching link: http://internal-host/..../apidocs/package-list. Ignored 
> it."
> This is a bug because this javadoc isn't accessible via http proxy.
> So I attached 2 patches :
> - the first one (link_nonproxy_2.0.10.patch) is compatible (and tested) with 
> mvn 2.0.9 and 2.0.10 but included a method directly copied from 
> ProxyUtils.java (wagon-provider-api-1.0-beta-6.jar)
> - the second (link_nonproxy_2.2.0.patch) used 2 classes from 
> wagon-provider-api-1.0-beta-6.jar dependency so it requires mvn 2.2

-- 
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


Reply via email to