Current behavior
OpenJDK 27 is now GA, but the Java bucket does not yet provide an openjdk27 manifest and the rolling openjdk manifest still discovers JDK 26 through its current checkver configuration.
The existing openjdk manifest checks:
https://jdk.java.net/archive/
This causes a problem during the transition to a new GA release: JDK 27 is the current release and is available from https://jdk.java.net/27/, but it is not yet listed on the archive page.
For example, after updating the manifest data to JDK 27:
.\bin\checkver.ps1 openjdk27
openjdk27: couldn't match ... in https://jdk.java.net/archive/
.\bin\checkver.ps1 openjdk
openjdk: 26.0.2.1-1 (scoop version is 27-35) autoupdate available
So the archive-based check currently either fails for a version-specific JDK 27 manifest or detects JDK 26 for the rolling manifest.
Proposed change
Add OpenJDK 27 GA support by:
- adding
bucket/openjdk27.json at version 27-35;
- updating the rolling
bucket/openjdk.json to version 27-35;
- using the current JDK 27 release page as the
checkver source while JDK 27 is the current GA release;
- retaining the existing captured-variable/autoupdate mechanism.
The Windows x64 GA artifact is:
https://download.java.net/java/GA/jdk27/55ce5470a6294008af0057ff4626d0e5/35/GPL/openjdk-27_windows-x64_bin.zip
SHA-256:
41172837168dd25a8d9fe5eb253ac1efc568c5f9ff608144bcacadfdf50f876c
Expected result
Users can install the current GA release with:
scoop install java/openjdk
or explicitly select JDK 27 with:
scoop install java/openjdk27
checkver.ps1 should also identify 27-35 rather than treating the latest archived JDK 26 release as an update.
Current behavior
OpenJDK 27 is now GA, but the Java bucket does not yet provide an
openjdk27manifest and the rollingopenjdkmanifest still discovers JDK 26 through its currentcheckverconfiguration.The existing
openjdkmanifest checks:https://jdk.java.net/archive/This causes a problem during the transition to a new GA release: JDK 27 is the current release and is available from
https://jdk.java.net/27/, but it is not yet listed on the archive page.For example, after updating the manifest data to JDK 27:
So the archive-based check currently either fails for a version-specific JDK 27 manifest or detects JDK 26 for the rolling manifest.
Proposed change
Add OpenJDK 27 GA support by:
bucket/openjdk27.jsonat version27-35;bucket/openjdk.jsonto version27-35;checkversource while JDK 27 is the current GA release;The Windows x64 GA artifact is:
SHA-256:
Expected result
Users can install the current GA release with:
scoop install java/openjdkor explicitly select JDK 27 with:
scoop install java/openjdk27checkver.ps1should also identify27-35rather than treating the latest archived JDK 26 release as an update.