From a236f6fb481d4042a83114ed6ff18ab202d26adb Mon Sep 17 00:00:00 2001
From: cpovirk <cpovirk@google.com>
Date: Mon, 26 Jun 2023 13:09:24 -0700
Subject: [PATCH] Update `guava-jre` instead of `guava-android`.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Since both flavors of Guava require Java 8+ nowadays (as [will jimfs](https://github.com/google/jimfs/issues/229)), I don't think there's an advantage of using `guava-android`.

I suppose that I could look into how much of `java.file.nio` can work [under new versions of Android](https://developer.android.com/reference/java/nio/file/Path) or [with desugaring](https://developer.android.com/studio/write/java11-nio-support-table). (Notably, do custom file systems work at all?) But my guess is that, in general, any Android code that can use `java.file.nio` can use `guava-jre`—though perhaps it shouldn't do _either_ of those things :)

RELNOTES=n/a
PiperOrigin-RevId: 543520082
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index 825a3cfc..92171f1e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -97,7 +97,7 @@
     <auto-service.version>1.1.1</auto-service.version>
     <auto-common.version>1.2.2</auto-common.version>
     <java.version>1.8</java.version>
-    <guava.version>32.0.1-android</guava.version>
+    <guava.version>32.0.1-jre</guava.version>
     <!--
       NOTE: When updating errorprone.version, also update javac.version to the
       version used by the new error-prone version. You should be able to find