[ http://jira.codehaus.org/browse/MRM-153?page=all ]

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

    Attachment: MRM-153.patch

This patch moves the relocation handling in DefaultProxyRequestHandler 
(archiva-proxy). No more change on archiva-core is required. 
Testcase is included for artecfact + checksum relocation on maven1 request.

This patch requires some logic change on the DefaultProxyRequestHandler.get() :
Artifact layout is discovered BEFORE proxies are used to get the file. This 
require to handle checksums, metadata and unknown file before requesting 
proxied repositories. 

I moved metadata and unknown files handling in a dedicated method to clarify 
code.

Please note this patch includes correction for issue MRM-155 as managed 
repository path is build during artifact discovery, so my patch for MRM-155 
gets obsolete if this patch is applied.

> 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, 
> DefaultProxyManager.java.patch, MRM-153-test.patch, MRM-153.patch, 
> MRM-155.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

        

Reply via email to