[
http://jira.codehaus.org/browse/MNG-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4528.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-7
Assignee: Benjamin Bentmann
Fixed in [r899004|http://svn.apache.org/viewvc?view=revision&revision=899004].
The root problem are the transitive dependencies of the Deploy Plugin versions
before 2.5 which under the revised class loading take precedence over the
default wagons from the distro. This made any bug of the old wagons come back.
> [regression] mvn deploy ignores proxy settings
> ----------------------------------------------
>
> Key: MNG-4528
> URL: http://jira.codehaus.org/browse/MNG-4528
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 3.0-alpha-6
> Environment: Vista, maven 3.0-alpha-6
> Reporter: Fred Bricon
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-7
>
>
> 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:
> {noformat}
> mvn deploy -Dhttp.proxyHost=proxy.ip -Dhttp.proxyPort=8080
> -Dhttp.proxyUser=username -Dhttp.proxyPassword=password
> {noformat}
> regards,
> Fred Bricon
--
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
