Geek Answers Handbook

Clojure / leiningen: The project suddenly broke! What can cause this maven error?

Go to run my clojure / lein app this morning and all of a sudden I get this error!

Retrieving lein-clojars/lein-clojars/0.9.1/lein-clojars-0.9.1.pom from clojars Retrieving lein-clojars/lein-clojars/0.9.1/lein-clojars-0.9.1.jar from clojars Could not find metadata org.codehaus.jackson:jackson-core-asl/maven-metadata.xml in local (/Users/JD/.m2/repository) Could not transfer metadata org.codehaus.jackson:jackson-core-asl/maven-metadata.xml from/to central (http://repo1.maven.org/maven2/): Checksum validation failed, expected e3f022e29dff365daf755e2c89fe42867e7addac but is aed947332fa98b1f9cd176faa3d046faa1e48bc9 Failure to find org.codehaus.jackson:jackson-core-asl/maven-metadata.xml in https://clojars.org/repo/ was cached in the local repository, resolution will not be reattempted until the update interval of clojars has elapsed or updates are forced This could be due to a typo in :dependencies or network issues. Could not resolve dependencies

Checksum error? On the jackson core? No typos or network problems (verified). What's going on here! Does anyone have a key?

Thanks!

+4
source share
2 answers

maven-metadata.xml for jackson-core-asl really has the MD5 file aed947332fa98b1f9cd176faa3d046faa1e48bc9 , while one leiningen calculated from the downloaded file is e3f022e29dff365daf755e2c89fe42867e7addac . This can happen when, for example, there is some network problem when loading an artifact from a remote repository: it may happen that in such cases the HTTP error code, such as 404, is ignored, and the hash is calculated from the HTML page describing the error.

Make sure you can achieve the artifact at least manually (i.e. there is no 404 or such), release

 rm -R ~/.m2/repository/org/codehaus/jackson

and try again.

+3
source

Aside from @skuro's answer, another common reason I ran into this problem is because you are behind an internal company repository (like nexus) that proxy centralizes. You should check your mirror parameter ~ / .m2 / settings.xml, and if you have such an internal repo, check its consistency with http://search.maven.org . Often the banks in your business repo are damaged and you need to remove it so that it reloads from the central

+3
source

More articles:


All Articles