[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256160#action_256160
]
Robert Glover Jr commented on MNG-4211:
---------------------------------------
I want to be clearer about the addition to settings.xml shown in the comment
above not working in maven version 2.1.0. I originally tested to my
satisfaction that it does not work (in maven 2.1.0) by testing with the version
of maven that comes prepackaged in the zip file for the newest version of the
Atlassian Plugin SDK (
http://confluence.atlassian.com/display/DEVNET/Atlassian+Plugin+SDK+Documentation
) .
To rule out that the version of maven (2.1.0) Atlassian's included in their
package "maven-2.1.0-uber.jar" is not the latest version of maven 2.1.0, I
just now went into the maven archives and downloaded/installed the latest
version of maven 2.1.0 and verified that when I test against "Apache Maven
2.1.0 (r755702; 2009-03-18 15:10:27-0400)"
I get this same "Unable to apply wagon configuration." error (which I do not
get in Maven 2.2.1) :
The reason this is a problem is that I cannot simply start using maven 2.2.1
for my specific need: the Atlassian Plugin SDK will only work with maven 2.1.0.
I confirmed that with the Atlassian Plugin developers at Atlassian.
So, since this JIRA is closed because MNG-4211 this is not a bug, I wonder
if a new JIRA should be opened for this specific inability to change the
User-Agent in version 2.1.0 of maven without getting a Wagon error?
> [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
> Assignee: Benjamin Bentmann
> Priority: Blocker
> 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
