[ 
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185933#action_185933
 ] 

John Casey commented on MNG-4211:
---------------------------------

@Sylvain-

Unfortunately, one of the bugfixes I had for RC1 addressed the single-download 
problem...but it got lost in version-control on my localhost, and didn't make 
it into RC1. This and the other issue with cross-pollution of wagon providers 
has been addressed in RC2.

I'm not sure about the need to set https.proxyHost/Port, though. Can you try 
out 2.2.1-RC2:

https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2

and report your results to the '[PLEASE TEST] Maven 2.2.1-RC2' thread out on 
the users or dev list? That would be a great help.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. 
> Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven 
> upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 
> and continues to work fine.  however maven via proxy always fails in version 
> 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the 
> creater of this JIRA and a maven developer.  2) two console outputs of 
> running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml 
> (with comments stripped out)

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