I don't think so, because the expected checksum is the correct checksum (at least, that's what I get when I manually checksum the jar in question):
384faa82e193d4e4b0546059ca09572654bc3970 *commons-fileupload-1.2.1.jar Steve From: Jack Krupansky [mailto:[email protected]] Sent: Friday, May 18, 2012 11:58 AM To: [email protected] Subject: Re: CHECKSUM FAILED for commons-fileupload-1.2.1.jar Maybe: <target name="jar-checksums" description="Recompute SHA1 checksums for all JAR files."> -- Jack Krupansky From: Smiley, David W.<mailto:[email protected]> Sent: Friday, May 18, 2012 11:48 AM To: mailto:[email protected] 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 /SmileyDev/Search/lucene-solr_svn/solr/lib/commons-fileupload-1.2.1.jar (expected: "384faa82e193d4e4b0546059ca09572654bc3970" was: "fd968960d004ba8863a2e7b9c88f260aa588c22d") I thought the fix for this is supposedly: ant clean-jars resolve But it didn't fix the issue. Any ideas? ~ David
