2 Replies Latest reply: Jun 15, 2011 9:24 AM by Mike Pettypiece RSS

Invalid repository-metadata.xml checksums

Chad La Joie Newbie

I'm proxying the public-jboss Maven repository, with Nexus, and am receiving errors that /.meta/repository-metadata.xml and its checksum don't match.  Sure enough, if I download that file and compute the MD5 and SHA1 checksums they definitely don't match the ones given.

 

Can anyone else confirm this?

  • 1. Re: Invalid repository-metadata.xml checksums
    Paul Gier Master

    Yes, these checksums are incorrect.  The same problem exists in the other repo groups also.  I'm not sure why though, I will check with Sonatype to see how to fix this.

  • 2. Re: Invalid repository-metadata.xml checksums
    Mike Pettypiece Newbie

    I'm not sure if this is related but many of the dependencies of:

     

    <dependency>
      <groupId>org.jboss.jbossas</groupId>
      <artifactId>jboss-as-client</artifactId>
      <version>6.0.0.Final</version>
      <scope>provided</scope>
      <type>pom</type>
    </dependency>
    

     

    have invalid SHA1 and MD5 checksums.  These are what I've found so far:

     

    <dependency>
       <groupId>org.jboss.classpool</groupId>
       <artifactId>jboss-classpool-scoped</artifactId>
       <version>1.0.0.Alpha6</version>
    </dependency>
    <dependency>
       <groupId>org.jboss.classpool</groupId>
       <artifactId>jboss-classpool</artifactId>
       <version>1.0.0.Alpha6</version>
    </dependency>
    <dependency>
       <groupId>org.jboss.classpool</groupId>
       <artifactId>jboss-classpool-jbosscl</artifactId>
       <version>1.0.0.Alpha6</version>
    </dependency>
    <dependency>
       <groupId>org.jboss.classpool</groupId>
       <artifactId>jboss-classpool-ucl</artifactId>
       <version>1.0.0.Alpha6</version>
    </dependency>
    <dependency>
       <groupId>org.jboss</groupId>
       <artifactId>jboss-reflect</artifactId>
       <version>2.2.0.Alpha6</version>
    </dependency>
    

     

    Manually specifying the GA releases does fix this issue.