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
