Update java.bzl best practices regarding HTTPS
While HTTP is faster and SHA256 already guaranteed data
hasn't been tampered with, it does give visibility over
the wire regarding which jars are being transmitted. The
true purpose of this change is to bring these practices
into greater consistency with Google's broader vision of
using HTTPS as much as possible.
PiperOrigin-RevId: 175328286
diff --git a/tools/build_defs/repo/java.bzl b/tools/build_defs/repo/java.bzl
index 7f3657b..766cb18 100644
--- a/tools/build_defs/repo/java.bzl
+++ b/tools/build_defs/repo/java.bzl
@@ -46,7 +46,6 @@
4. Make the second URL the original repo1.maven.org URL
5. Make the third URL the maven.ibiblio.org mirror, if it isn't 404
6. Always specify the sha256 checksum
-7. Prefer http over https unless curl -I says the http URL redirects to https
Bazel has one of the most sophisticated systems for downloading files of any
build system. Following these best practices will ensure that your codebase
