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

Frank Cornelis commented on MNG-4211:
-------------------------------------

Apparently 2.2.1 still has some proxy issues. At work I'm having difficulties 
compiling my software because we're sitting behind a proxy over there. I have a 
mixture of both http and https repositories, and this doesn't really work 
apparently. At home (direct connection) the build works as expected.

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