Bad checksums for guice artifacts in Maven repository

[GoogleCodeExporter]

Hello.

There are bad checksums for files in Maven repository for guice and 
parent-guice artifacts.

For example:

http://google-maven-repository.googlecode.com/svn/repository/com/google/inject/g
uice-parent/2.0/guice-parent-2.0.pom

has md5 checksum = b27190451be907f14ac4dbf914f1320d in 
guice-parent-2.0.pom.md5, and sha1 checksum in guice-parent-2.0.pom.sha1 = 
46a326d1fb2d17034161c9a7346978ea248a9643 when the actual checksums for the file 
are:

md5: faaf81173221660334ae8c274503b860
sha1: f145896f8cc8a0729cda33fa3cde90f6c9b8969c

Same applies for com/google/inject/guice/2.0/guice-2.0.jar and 
com/google/inject/guice/2.0/guice-2.0.pom

It seems that the problem exists only for version 2.0.

Original issue reported on code.google.com by rafalg...@gmail.com on 28 Feb 2014 at 12:05

[GoogleCodeExporter]

While this is an annoyance, are people still using the Guice 2.0 artifacts?  I 
believe that the 2.0 line in the source repository has not been built in ages, 
and I don't even know if it has a correct setup to generate maven artifacts.  

Original comment by christia...@gmail.com on 28 Feb 2014 at 5:04

• Changed state: NeedInfo

[GoogleCodeExporter]

Also since Guice 2.0 is available on Maven central: 
http://search.maven.org/#artifactdetails%7Ccom.google.inject%7Cguice%7C2.0%7Cjar
 you shouldn't need to use this separate repository anymore.

Original comment by mccu...@gmail.com on 28 Feb 2014 at 6:10

[GoogleCodeExporter]

Oh god - I totally misread it.  Yeah - I'm inclined to remove these entirely 
from the google-maven-repository.  Good catch Stuart. 

Original comment by christia...@gmail.com on 28 Feb 2014 at 6:38

• Changed state: Obsolete