[
http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213521#action_213521
]
Anders Hammar commented on MNG-4469:
------------------------------------
I can confirm that a deploy with altDeploymentRepository doesn't not work with
auth in Maven 3.0-alpha-6. It does work with Maven 2.2.1 though.
Here my command:
mvn deploy
-DaltDeploymentRepository=repo-xxx::default::http://repo-xxx/content/repositories/releases
A server with id 'repo-xxx' is defined in my settings.xml.
In Nexus I see that the access is with no auth info (Nexus says anonymous).
Should this issue be reopened or do you want me to submit a new jira?
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories
> on its own will appear to ignore mirror, proxy and authentication infos from
> the settings when run with Maven 3.0. This is due to the
> {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and
> not injecting these infos any longer automatically.
--
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
