You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2008/12/21 03:45:20 UTC

[jira] Updated: (MNG-3932) Remove all mirror, authentication, and proxy handling out of WagonManager and into a neutral Maven implementation

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

Jason van Zyl updated MNG-3932:
-------------------------------

    Fix Version/s: 3.0-alpha-2

> Remove all mirror, authentication, and proxy handling out of WagonManager and into a neutral Maven implementation
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3932
>                 URL: http://jira.codehaus.org/browse/MNG-3932
>             Project: Maven 2
>          Issue Type: Task
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>             Fix For: 3.0-alpha-2
>
>
> We need to protect ourselves from the underlying transport implementation. Mercury will only touch Maven inside one component, so this is what I'm going to create on a branch where Wagon only touches Maven inside one component. I can't really implement the plugin manager properly without hardcoding because I can't get the correct mirror information to Mercury without wiring in the WagonManager which I'm not going to do. I'm just going to do it properly. We won't have extension support in alpha-1. Oh well.

-- 
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