[ http://jira.codehaus.org/browse/MRM-153?page=comments#action_73861 ] Brett Porter commented on MRM-153: ----------------------------------
there are a number of issues with this that I am reworking: - the same ones highlighted in MRM-155 - incorrect assumptions about the location of the POM - didn't test m2 relocations at all - exception handling in the relocation was not ideal - applyRelocation didn't need to return artifact, it modifies the passed in instance > 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
