You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/07/31 20:02:26 UTC

[jira] Commented: (WAGON-234) deprecated proxyInfo parameter for Wagon.connect(..) doesn't work in 1.0-beta-4

    [ http://jira.codehaus.org/browse/WAGON-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143782#action_143782 ] 

Brett Porter commented on WAGON-234:
------------------------------------

can you elaborate on the circumstances that caused this?

it is set, and is intended to be used as a fallback, but perhaps one particular sequence doesn't do this

> 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