maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRM-153) when used as a maven1 proxy, Archiva should handle relocation from maven2 poms
Date Mon, 28 Aug 2006 08:49:48 GMT
     [ http://jira.codehaus.org/browse/MRM-153?page=all ]

nicolas de loof updated MRM-153:
--------------------------------

    Attachment: DefaultProxyManager.java.patch

Patch updated for "archiva" renamed project.

> when used as a maven1 proxy, Archiva should handle relocation from maven2 poms
> ------------------------------------------------------------------------------
>
>                 Key: MRM-153
>                 URL: http://jira.codehaus.org/browse/MRM-153
>             Project: Archiva
>          Issue Type: Improvement
>         Environment: Archiva as a repository proxy for maven1
>            Reporter: nicolas de loof
>            Priority: Minor
>         Attachments: DefaultProxyManager.java.patch, patch.patch
>
>
> When a maven1 client asks for /servletapi/jars/servletapi-2.4.jar, Archiva converts path
to the maven2 location of this artifact. As maven1 has no relocation support, the jar is required
in the repo. 
> Archiva can be more that a proxy : download the artifact POM, read relocation infos,
and return the relocated jar.
> attached Patch add a new "applyRelocation" to DefaultProxyManager.
> I've tried this code with the servletapi example, but it may be bad designed as I just
discovered maven / archiva APIs.

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

        

Mime
View raw message