[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185404#action_185404 ]
Sylvain Marié commented on MNG-4211:
------------------------------------
Hi John, I've tried your 2.2.1-RC1 and it helps to solve this issue (but there is still a bug because
<configuration>
<wagonProvider>lightweight</wagonProvider>
</configuration>
is used only for one dependency download: if there are several dependencies in this repository it hangs. This doe not happen if the configuration is provided by commandline option
-Dmaven.wagon.provider.http=lightweight -Dmaven.wagon.provider.https=lightweight
, as described in the email I sent you. There is also a big side-effect for us since it seems to impact other wagons, in particular the wagon-svn, see email)
Anyway it is strange because even with RC2.2.1, I have additionally to set java proxy features for https in the mvn.bat script (-Dhttps.proxyHost and -Dhttps.proxyPort). I remember a time (maybe maven 2.0.6 ?) where this was not needed, and where maven worked fine with our proxy using just the settings' <proxies> section. It is sad that this behaviour is now lost..
Best regards,
Sylvain
> [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.2
>
> 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
