See if the downloaded jars actually match if you download it and compare it to your local one using shasum. If they don't match, unzip them and see what's different.
-Tim On Mon, Mar 12, 2018 at 8:48 PM Christian Bourque < [email protected]> wrote: > Hi all, > > I'm currently trying to compile NetBeans 9.0 with a more recent Eclipse > JGit library (the one currently bundled with > NetBeans is 3 years old!) but I'm having a hard time with the hash (sha1) > value that is used by the build system that's > downloading the artefact from the Maven Central repository! When I build > NetBeans it says that the hash value > that I put in the binaries-list file doesn't match the hash of the artefact > found on Maven Central, but I took the hash > value directly from the Maven Central repository so I expected it to be > correct: > > http://central.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.11.0.201803080745-r/ > > So then I decided to download the Eclipse JGit source code from GitHub: > https://github.com/eclipse/jgit/releases/tag/v4.11.0.201803080745-r > compile it and generate the sha1sum myself. To my surprise the computed > checksum was equal to the one expected by NetBeans during the build > process. > > So I'm a bit puzzled! If the build script is downloading an external > dependency from Maven Central then the hash should > match the one found in this file: > > http://central.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.11.0.201803080745-r/org.eclipse.jgit-4.11.0.201803080745-r.jar.sha1 > > Anyway, if anyone could shed some light on this situation I would really > appreciate it! > > Thanks, > > Christian > -- http://timboudreau.com
