You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This brings us to the newest released version, which also means that it matches the version that we use for javac, so we require one less JDK.
cl/711811272 fixed [the error we'd previously been seeing with JDK 23](google#6790 (comment)).
(Also, if someone has a JDK 23 already installed and skips our auto-downloading, use it even if it's not Temurin. I'd made this change for most toolchain usages in cl/711746683, but I missed the usage one for Javadoc.)
RELNOTES=n/a
PiperOrigin-RevId: 711839263
Copy file name to clipboardExpand all lines: .github/workflows/ci.yml
+2-7Lines changed: 2 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -40,14 +40,12 @@ jobs:
40
40
# When we specify multiple JDKs, the final one becomes the default, which is used to execute Maven itself.
41
41
# Our Maven configuration then specifies different JDKs to use for some of the steps:
42
42
# - 11 (sometimes) to *download* to support anyone who runs JDiff or our Gradle integration tests (including our doc snapshots and our Java 11 CI test run) but not to use directly
43
-
# - 21 for building Javadoc
44
-
# - 23 for running javac (to help people who build Guava locally and might not use a recent JDK to run Maven)
43
+
# - 23 for running Javadoc and javac (to help people who build Guava locally and might not use a recent JDK to run Maven)
0 commit comments