mirror of
https://github.com/actions/setup-java.git
synced 2026-08-25 16:00:54 +00:00
2b61aea53d
A floating Oracle JDK or Oracle GraalVM request now skips the tool-cache short-circuit entirely, so every job re-downloads and re-extracts the JDK even when the exact bytes the mutable URL currently serves are already installed locally. The JDK resolution cache is keyed on the artifact's checksum (or, failing that, its HTTP response fingerprint), so a hit proves which concrete version the URL is serving right now. Once it has vouched for that version, an existing tool-cache installation of exactly that version is the artifact the download would have produced, and can be reused. Reuse is therefore gated on the resolution cache hit, never on the requested major: an unidentified floating artifact still downloads, as does an explicit force-download. Co-authored-by: Bruno Borges <brunoborges@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f2d9a891-a680-4b35-9644-cf2450f76f6d |
||
|---|---|---|
| .. | ||
| cache | ||
| data | ||
| distributors | ||
| auth.test.ts | ||
| benchmark-cache-restore.sh | ||
| cache-feature.test.ts | ||
| cache.test.ts | ||
| check-dir.sh | ||
| checksum.test.ts | ||
| cleanup-java.test.ts | ||
| gpg.test.ts | ||
| java-package-contract.test.ts | ||
| java-platform-contract.test.ts | ||
| jdk-cache.test.ts | ||
| jdk-resolution-cache.test.ts | ||
| maven-args.test.ts | ||
| maven-xml-loading.test.ts | ||
| problem-matcher.test.ts | ||
| retrying-http-client.test.ts | ||
| setup-java.module-loading.test.ts | ||
| setup-java.test.ts | ||
| toolchains.test.ts | ||
| util-install.test.ts | ||
| util.test.ts | ||
| verify-java.sh | ||