[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180878#action_180878
]
Robert Glover Jr commented on MNG-4211:
---------------------------------------
I will investigate whether there is a legitimate way for me to provide that
information. I agree it seems ridiculous that I can't provide such basic
information in this context when the company is totally anonymous and entirely
obfuscated in the JIRA. I will do what I can but it's an uphill battle to say
the least..
Please notice what I found from a google of "Wagon 1.0-beta-4". (See below).
It does look like change WAGON-225 might be the culprit, don't you think?
The Wagon 1.0-beta-4 candidate has been staged.
This release includes 4 fixes. You can take a look at the release
notes here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=14310
* [WAGON-222] - Empty file transfer causes NPE
* [WAGON-224] - ChecksumObserver sets digest == null on transfer
error, leading to NPE's if checksum downloads are retried with same
observer instance
* [WAGON-225] - proxyInfoProvider is never used
* [WAGON-226] - filePermissions and directoryPermissions are not set
correctly for FTP
> [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
