Details
-
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
-
Labels:None
-
Environment:Vista, maven 3.0-alpha-6
-
Complexity:Intermediate
-
Number of attachments :
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
Fixed in r899004.
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.