Re: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

And for those that are curious, the difference between the valid jar (as identified by the checksum sha1 in Solr) and the one I had with a different checksum, is that the "bad" one was built ~40 seconds earlier, as reflected in a comment date in META-INF/maven/commons-fileupload/commons-fileupload/

Re: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

Thanks Steve. What I ended up doing was removing this particular artifact from my ivy cache, which triggered a re-download. Now I'm all curious what precisely changed. ~ David On May 18, 2012, at 11:53 AM, Steven A Rowe wrote: I think this can happen when your Ivy cache gets corrupted, and can

RE: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

nt: Friday, May 18, 2012 11:58 AM To: dev@lucene.apache.org Subject: Re: CHECKSUM FAILED for commons-fileupload-1.2.1.jar Maybe: -- Jack Krupansky From: Smiley, David W.<mailto:dsmi...@mitre.org> Sent: Friday, May 18, 2012 11:48 AM To: mailto:dev@lucene.apache.org Subject: CHECKSUM FA

Re: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

Maybe: -- Jack Krupansky From: Smiley, David W. Sent: Friday, May 18, 2012 11:48 AM To: mailto:dev@lucene.apache.org Subject: CHECKSUM FAILED for commons-fileupload-1.2.1.jar I'm trying to build Lucene/Solr today, svn updated, then went to do a compile and I got this: CHECKSUM FAILED for

RE: CHECKSUM FAILED for commons-fileupload-1.2.1.jar

I think this can happen when your Ivy cache gets corrupted, and can be fixed by clearing the Ivy cache, triggering a re-download. (To automate this, we could wrap the ant task: .) Steve From: Smiley, David W. [mailto:dsmi...@mitre.o