Greetings, I use a Maven Repository Manager (and so should you!) to proxy many other repositories. I updated it today to point to the new location, repo.jenkins-ci.org, however it isn't serving up proper hashes for at least one important artifact:
http://repo.jenkins-ci.org/repo/org/jenkins-ci/main/jenkins-war/1.447.2/jenkins-war-1.447.2.war.sha1 By default, I think most MRMs will reject proxying an artifact if the sha does not match the download. So this is causing other builds to fail because dependencies can not be fetched.. Can someone look into this please? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
