You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/06/18 23:21:15 UTC
[jira] Updated: (MNG-4211) [regression] proxy access broken between
maven version 2.0.10 and 2.1. Probably due to addition of wagon
1.0-beta-4+
[ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-4211:
----------------------------
Priority: Blocker (was: Major)
Fix Version/s: 3.0-alpha-3
2.2.1
Summary: [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+ (was: ability to use maven via proxy stopped between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+)
I'll have to do some poking around here locally with a proxy appliance, but the problem is complicated by the fact that many users configure proxies for use with Maven, and there seem to be no other problem reports like this one.
Without knowing what type of proxy is causing this problem, it's going to be very difficult to fix.
> [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