Remove default MD5 in most of Bazel's virtual filesystems.

This forces the ex-default to be explicit in a lot of tests, but I'd rather that than have the risk of implicit md5-use in production code.

To keep this CL smaller, do not remove the default from UnixFS quite yet.

RELNOTES: None.
PiperOrigin-RevId: 206223521

1 files changed, 3 insertions, 2 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/vfs/JavaIoFileSystem.java b/src/main/java/com/google/devtools/build/lib/vfs/JavaIoFileSystem.java
index 1fec03f5db..00a320fa57 100644
--- a/src/main/java/com/google/devtools/build/lib/vfs/JavaIoFileSystem.java
+++ b/src/main/java/com/google/devtools/build/lib/vfs/JavaIoFileSystem.java
@@ -53,7 +53,7 @@ public class JavaIoFileSystem extends AbstractFileSystemWithCustomStat {
   protected static final String ERR_NOT_A_DIRECTORY = " (Not a directory)";
 
   public JavaIoFileSystem() {
-    this(new JavaClock());
+    this(new JavaClock(), DigestHashFunction.MD5);
   }
 
   public JavaIoFileSystem(DigestHashFunction hashFunction) {
@@ -62,7 +62,8 @@ public class JavaIoFileSystem extends AbstractFileSystemWithCustomStat {
   }
 
   @VisibleForTesting
-  JavaIoFileSystem(Clock clock) {
+  JavaIoFileSystem(Clock clock, DigestHashFunction hashFunction) {
+    super(hashFunction);
     this.clock = clock;
   }