[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256054#action_256054
]
Robert Glover Jr commented on MNG-4211:
---------------------------------------
I have verified that by using the <server> configuration shown in the
preceeding comment, I can do a successful Maven "package" in maven version
2.2.1. However I get a "wagon" failure when I use the exact same settings.xml
file but change the version of maven to either version 2.0.11 or version 2.1.0.
(And of course, maven 2.0.9 and below always work and do not need that
<server> configuration shown in the comment at all.
To be completely clear about this, at the bottom of this comment I pasted
the 2 <server> additions I use in settings.xml. It works perfectly in maven
2.2.1, it is not needed in maven 2.0.9 and below, and it causes a "wagon"
error message and does not work in maven 2.0.11 and maven 2.1.0.
The error message I get running version 2.0.11 is "Unable to apply wagon
configuration." (see below). Same error occurs in maven 2.1.0
[INFO] ------------------------------------------------------------------------
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository
central (http://repo1.maven.org/maven2): While configuring wagon for 'central':
Unable to apply wagon configuration.
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository nexus
(http://b1bsdzv03:8082/nexus/content/groups/public): While configuring wagon
for 'nexus': Unable to apply wagon configuration.
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository
central (http://repo1.maven.org/maven2): While configuring wagon for 'central':
Unable to apply wagon configuration.
[INFO] ------------------------------------------------------------------------
<servers>
<server>
<id>nexus</id>
<configuration>
<wagonProvider>httpclient</wagonProvider>
<httpHeaders>
<property>
<name>User-Agent</name>
<value>Java/1.6.0_21</value>
</property>
</httpHeaders>
</configuration>
</server>
<server>
<id>central</id>
<configuration>
<wagonProvider>httpclient</wagonProvider>
<httpHeaders>
<property>
<name>User-Agent</name>
<value>Java/1.6.0_21</value>
</property>
</httpHeaders>
</configuration>
</server>
> [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
