[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255304#action_255304
]
Robert Glover Jr commented on MNG-4211:
---------------------------------------
Benjamin, my associate took a look at your response and especially the
link you provided: http://maven.apache.org/guides/mini/guide-http-settings.html
His reply indicates to me that it would be incredibly helpful if you could
provide a a simple step-by-step explanation on how to change the user agent
header-- ideally in your next comment here. (Hopeful, wistful smile).
Here are my associates's 2 comments:
First comment: Unfortunately it doesn't say anything about the user agent
header. And the whole thing is pretty confusing.
Second comment in a subsequent email: I re-read it and tried again to follow
the instructions but was unsuccessful. The user agent doesn't change.
> [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 & 3
> 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: Issues to be reviewed for 3.x
>
> 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
