maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (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+
Date Tue, 08 Feb 2011 17:33:22 GMT

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

Benjamin Bentmann commented on MNG-4211:
----------------------------------------

Thanks for the info, the change in user agent is due to MNG-3652. You could try the [advanced
HTTP config|http://maven.apache.org/guides/mini/guide-http-settings.html] to force another
agent or in Maven3 add {{-Daether.connector.userAgent=desired-agent}} to your {{MAVEN_OPTS}}.
But in the long run, you should probably talk to the firewall maintainer to allow the Maven's
requests to pass through, with their original user agent info. 

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

        

Mime
View raw message