[
http://jira.codehaus.org/browse/WAGON-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143794#action_143794
]
Brett Porter commented on WAGON-234:
------------------------------------
I'll take a look - Wagon itself now uses the provider, and a default one using
the proxyInfo is constructed in that constructor. The old field is there for
anyone using it since it was a protected variable.
I'm quite sure the ITs worked with the old constructor - but good that it is
working now.
> deprecated proxyInfo parameter for Wagon.connect(..) doesn't work in
> 1.0-beta-4
> -------------------------------------------------------------------------------
>
> Key: WAGON-234
> URL: http://jira.codehaus.org/browse/WAGON-234
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-4
> Reporter: John Casey
> Fix For: 1.0-beta-5
>
>
> proxyInfo parameter passed into some connect(..) methods is set on the
> AbstractWagon instance, but is never used. This will probably cause problems
> for users of older versions of wagon, as it did with DefaultWagonManager in
> maven-artifact-manager 2.0.10-RC4 snapshot, until I traced it back and
> learned that I had to provide a ProxyInfoProvider instance instead to get
> proxies working.
--
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
