Another hack (that I've seen, but can't take credit for) is to walk the directory of your corp repo and regenerate the checksums. Call this in a cron.
#!/bin/sh # Recurse through subdirectories, creating missing checksums needed for Maven. export REPO_ROOT=/path/to/corp/repo cd $REPO_ROOT for i in `find . -name "*.jar"` do openssl md5 < $i > $i.md5 openssl sha1 < $i > $i.sha1 done for i in `find . -name "*.pom"` do openssl md5 < $i > $i.md5 openssl sha1 < $i > $i.sha1 done Jim On 9/25/07, Martin Pruefer <[EMAIL PROTECTED]> wrote: > > Hi, > > try setting the checksum policy in your repository definition, like in > this snippet from a pom.xml: > > [...] > <repository> > <releases> > <enabled>true</enabled> > <checksumPolicy>ignore</checksumPolicy> > </releases> > <id>internal-m2repo</id> > <name>Internal Maven2 Repository</name> > <url>http://mavenrep.mycompany.com/m2repo</url> > </repository> > [...] > > On 9/25/07, Angel Sotirov <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Is there a way to resolve the annoying *** CHECKSUM FAILED from > > internal remote archiva repository? > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Martin Pruefer *** [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
