[jira] Commented: (MJAVADOC-253) Http proxy does not work any more

["Mohan K (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215641#action_215641 ] 

Mohan K commented on MJAVADOC-253:
----------------------------------

Hello Vincent,
 Sorry could not get back on this, it appears that we do have NTLMv2 proxy. So the plugin change to commons-httpclient
 is really put a blocker to move to 2.6.x version of the plugin.
 
 A potential fix would be to provide a plugin option to choose the built-in JDK and default to commons-httpclient.

 But for those who are requiring to use 2.6.1, the workaround is to use the additionalparam option and turn
 of all detection and resolution by the javadoc plugin. Which means some of the automatic detection features
 of 2.6.x would have to be sacrificed.
 
 An e.g. would be
          <detectJavaApiLink>false</detectJavaApiLink>
          <detectOfflineLinks>false</detectOfflineLinks>
          <detectLinks>false</detectLinks>
          <additionalJOption>-J-Dhttp.proxySet=true -J-Dhttp.proxyHost=proxy.somewhere.com -J-Dhttp.proxyPort=3128 -J-Dhttp.nonProxyHosts="java.sun.com|*.somewhere.com" \
    -J-Dhttp.proxyUser="foo" -J-Dhttp.proxyPassword="bar" </additionalJOption>

          <additionalparam>
            -link http://java.sun.com/javase/6/docs/api
          </additionalparam>

 NOTE: you must not use the
   <link>, <linkoffline> tags, just delegate it to the javadoc exe.

  

> Http proxy does not work any more
> ---------------------------------
>
>                 Key: MJAVADOC-253
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-253
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6
>         Environment: Maven 2.0.9
> JDK5 (Sun)
>            Reporter: Mohan K
>            Priority: Critical
>
> It appears the update of Wagon Provider in 2.6 is not compatible with Maven 2.0.x. Here is the
> email snippet as posted to maven users group (no responses)
> I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the "links" configured in my
> plugin config. Now all resolution of external links fail (we are behind a proxy *not* NTLM)
> with this:
> Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
> INFO: ntlm authentication scheme selected
> Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector authenticate
> The wagon provider appears to have been upgraded to 1.0-beta-6 in the maven-javadoc-plugin 2.6
> (as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is wrong) that wagon 1.0-beta-6
> requires Maven 2.1.x and above? If that is the case, I don't understand how the plugin was released with
> prerequisite of 2.0.9? 
> Is there a workaround to disable the default ntlm auth scheme via a magical system property? TIA 

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