[MNG-4528] [regression] mvn deploy ignores proxy settings

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-6
• Fix Version/s: 3.0-alpha-7
• Component/s: Deployment
• Environment: Vista, maven 3.0-alpha-6
• Assignee: Benjamin Bentmann
• Reporter: Fred Bricon
• Created: 12/Jan/10 04:15
• Updated: 06/Apr/15 01:53
• Resolved: 13/Jan/10 18:13

Description

Running "mvn deploy" fails when behind a proxy (connection refused) in maven 3.0-alpha6, even though the proxy settings have been configured in settings.xml.

Deploying the same artifact succeeds when using maven 2.0.10 -> 2.2.1, using the same settings.xml.
As a workaround, I had to add pass the proxy parameters in the command line:

mvn deploy -Dhttp.proxyHost=proxy.ip -Dhttp.proxyPort=8080 -Dhttp.proxyUser=username -Dhttp.proxyPassword=password

regards,

Fred Bricon

Issue Links

• is related to: WAGON-236 LightweightHttpWagon is not using proxy settings
• is related to: MNG-4470 [regression] Proxies are ignored during artifact deployment
• relates to: MNG-4561 [regression] network settings are not applied to repositories from plugin dependencies