[MNG-4478] deploy plugin altDeploymentRepository does not use authorization credentials

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0-alpha-4, 3.0-alpha-5
• Component/s: Deployment
• Assignee: Benjamin Bentmann
• Reporter: Marc Wirth
• Created: 02/Dec/09 10:15
• Updated: 02/Dec/09 10:20
• Resolved: 02/Dec/09 10:20

Description

When using the altDeploymentRepository of the deploy plugin (2.4 or 2.5-SNAPSHOT) the (Default)ArtifactRepository will have no Authorization object set, thus deployment will fail if the repository requires authorization.

My expectation was that authorization credentials are picked up if a <server> with matching ID is configured in the settings.xml.

The attached patch fixes this the hard way in the deploy plugin, but the change requires building the deploy plugin against maven 3.0-alpha. I think this should rather be fixed in Maven itself if possible, but I don't know how to do that.

Issue Links

• duplicates: MNG-4469 [regression] deploy:deploy-file fails with secured repository