[JAVA-1879] Wrong maven checksum Created: 03/Jul/15  Updated: 06/Jul/15  Resolved: 06/Jul/15

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Rinat Muhamedgaliev Assignee: Unassigned
Resolution: Done Votes: 0
Labels: driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu 12.04 LTS, SBT 0.13.8



 Description   

[info] Resolving org.mongodb#mongo-java-driver;3.0.2 ...
[warn] problem while downloading module descriptor: https://repo1.maven.org/maven2/org/mongodb/mongo-java-driver/3.0.2/mongo-java-driver-3.0.2.pom: invalid sha1: expected=62941f96886d10abb424439466a091b2c31a1c18 computed=aa964994e3251370a1f9431a486ea8c722ae52b5 (264ms)
[warn] problem while downloading module descriptor: http://repo1.maven.org/maven2/org/mongodb/mongo-java-driver/3.0.2/mongo-java-driver-3.0.2.pom: invalid sha1: expected=62941f96886d10abb424439466a091b2c31a1c18 computed=aa964994e3251370a1f9431a486ea8c722ae52b5 (222ms)
[warn] module not found: org.mongodb#mongo-java-driver;3.0.2

Can't build project because, can't resolve driver.



 Comments   
Comment by Ross Lawley [ 06/Jul/15 ]

Thanks again rinat.muhamedgaliev@gmail.com for reporting this. Having spoken to Sonatype, there was an issue on their side with a number of metadata files in various mongodb repos.

The reasons for the corruption wasn't explained but they have fixed the metadata and this is propagating back to maven central.

All the date timestamps are back to normal: http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.0.2/

Comment by Ross Lawley [ 03/Jul/15 ]

Hi rinat.muhamedgaliev@gmail.com,

Thanks for making us aware, I'm investigating how this has happened as maven releases are federated from sonatype.

In the meantime please add sonatype to your resolvers and then it will work as expected: https://oss.sonatype.org/content/repositories/releases/org/mongodb/mongo-java-driver/3.0.2/

Generated at Thu Feb 08 08:55:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.