[
https://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-253.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
Assuming this works with Maven-2.2.1, which is the current prerequisite for the
plugin.
> Http proxy does not work any more
> ---------------------------------
>
> Key: MJAVADOC-253
> URL: https://jira.codehaus.org/browse/MJAVADOC-253
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.6, 2.7
> Environment: Maven 2.0.9
> JDK5 (Sun)
> Reporter: Mohan K
> Assignee: Robert Scholte
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
