[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180874#action_180874
]
Wayne Fay commented on MNG-4211:
--------------------------------
> Without knowing what type of proxy is causing this problem, it's going to be
> very difficult to fix.
Which is what I told Robert originally on the Users list... One way or another,
you're going to have to get us that information, Robert. Even if you're
forbidden from asking or passing it on. Big companies are so stupid sometimes
-- I would know, I've worked for several of them.
> [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.1, 3.0-alpha-3
>
> 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
