You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Quintin Beukes <qu...@last.za.net> on 2009/10/19 21:00:27 UTC

Fwd: Central Artifact Metadata Outdated

I'm not sure if you guys are in charge of deploying the XBean project
to the Maven Central repository, but I'm getting the following and
they said the problem is on the deployer's side.

Message follows:
-------------------------------------------------------
Hey,

I'm getting the following, repeatedly. It's being downloaded via
Nexus, but I repeatedly get the following messages (everytime it's
checked for updates):

Downloading: http://blade:7081/nexus/content/groups/public/org/apache/xbean/xbean-asm-shaded/3.6/xbean-asm-shaded-3.6.jar
118K downloaded  (xbean-asm-shaded-3.6.jar)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0a394260d8d16ba233796bc68b5f4188442e37fe'; remote =
'3e5ce3998772b6a8ccd401ee1caf33fd8949c8d2' - RETRYING
Downloading: http://blade:7081/nexus/content/groups/public/org/apache/xbean/xbean-asm-shaded/3.6/xbean-asm-shaded-3.6.jar
118K downloaded  (xbean-asm-shaded-3.6.jar)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0a394260d8d16ba233796bc68b5f4188442e37fe'; remote =
'3e5ce3998772b6a8ccd401ee1caf33fd8949c8d2' - IGNORING

I checked the download at central, and the file's sha1sum against the
metadata file's value differs. Manually verifying gives the same
results as in the errors above.

Who manages Central, iow. how should I report this?

Quintin Beukes

Re: Central Artifact Metadata Outdated

Posted by Kevan Miller <ke...@gmail.com>.
On Oct 19, 2009, at 3:00 PM, Quintin Beukes wrote:

> I'm not sure if you guys are in charge of deploying the XBean project
> to the Maven Central repository, but I'm getting the following and
> they said the problem is on the deployer's side.

Thanks Quintin. This looks like the MAVEN 2.2 bug which causes a  
checksum error on files uploaded to the nexus. Think we found the  
problem with our jaspic release, but Maven 2.2 must have been used for  
the XBean release. David J, didn't you get some help with this when we  
found the jaspic problem? Think we can enlist a little more assistance?

--kevan