Did you/can you check the contents of the bad jars ? Kristian
2013/9/26 jieryn <jie...@gmail.com>: > Greetings, > > On Wed, Sep 25, 2013 at 11:05 PM, Jason van Zyl <ja...@tesla.io> wrote: >> Does 3.1.0 not display this behaviour? >> >> On Sep 25, 2013, at 6:41 PM, jieryn <jie...@gmail.com> wrote: >>> Archive for required library: >>> '$HOME/.m2/repository/$GROUPID/$ARTIFACTID/$VERSION/$FINALNAME.jar' in >>> project 'test' cannot be read or is not a valid ZIP file > > We've run about 2000 builds on Jenkins using 3.1.0 and none have > failed in that manner. On my workstation, where I am seeing the > problem, I have run perhaps thousands of builds using 3.1.0 and I > don't remember seeing the problem.. > > Other folks are reporting these errors on the Apache Archiva mailing > lists. However, without any evidence to support it, I do not think it > is immediately an Archiva problem--I think it is 3.1.1. Given how > seldom I have seen it, and how easy it is to fix after the fact (just > rm -rf $(dirname $bad.jar)) maybe the best thing to flush out this one > is to complete 3.1.1 release. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
