I've attached a patch to http://jira.codehaus.org/browse/MRM-155
This patch changes the artifact proxying process : When the
legacyDiscovery is used by a proxied repo to convert path to artifact,
the maven2 path is build and the target file is overriden.
Brett Porter a écrit :
On 24/08/2006, at 5:48 PM, Nicolas De Loof wrote:
I also noticed this :
When Archiva downloads a maven1 artifact, (let's say servletapi-2.3
if relocation isn't used) the checksum is stored in repo using a
maven2 path, but the artifact is stored using original maven1 path.
This may produce lot's of duplicates in the managed repo.
-> servletapi\servletapi\2.3\servletapi-2.3.jar.sha1
-> servletapi\jars\servletapi-2.3.jar
When a maven2 client asks for it, the artifact is downloaded a second
time
-> servletapi\servletapi\2.3\servletapi-2.3.jar
I'll investigate this...
Did you find anything? Is it dependant on the format of the managed
repository itself, or only what the proxy requests of it?
- Brett
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
