archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter" <brett.por...@gmail.com>
Subject Re: Archiva selectively failing to proxy one particular artifact
Date Sat, 01 Mar 2008 00:04:06 GMT
On 01/03/2008, Brown, Carlton <Carlton.Brown@compucredit.com> wrote:
> OK thanks, I figured out what's going on.  The checksum was failing for
>  http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.p
>  om
>
>  Testing confirms that it seems the checksums in the central repo are
>  wrong.  I manually ran md5 and sha1 sums on that file, and they do not
>  match the sums stored in central.  By comparison, the pom for 2.0.7 does
>  not have this problem.
>
>  Having confirmed this, if I could beg your indulgence for a couple of
>  followup questions:
>
>  1)  You said you didn't have this problem... I presume you have
>  checksumming set to 'ignore' or 'fix' in Archiva?

right

>  2)  Is a 404 really the only error we get on this problem?  This is the
>  same thing you'd get for a completely nonexistent artifact, it's kind of
>  misleading.

we're looking to fix that for 1.0.2:
http://jira.codehaus.org/browse/MRM-159

>  3)  (Rhetorical question) WTF is up with Maven central having bad
>  checksums for Maven's own artifacts, and how can I be the first one to
>  notice this?  Did I make some mistake, or is everyone except me ignoring
>  checksums?

Yeah, I remember 2.0.6 coming up - I'm not sure why it was never fixed.

- Brett

-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Mime
View raw message