You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/08 18:14:55 UTC

[jira] Closed: (MNG-4469) [regression] deploy:deploy-file fails with secured repository

     [ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4469.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-alpha-6
         Assignee: Benjamin Bentmann

Fixed in [r888488|http://svn.apache.org/viewvc?view=revision&revision=888488].

> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
>                 Key: MNG-4469
>                 URL: http://jira.codehaus.org/browse/MNG-4469
>             Project: Maven 2
>          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