suresh
10/22/2026, 11:47 PMsuresh
10/22/2026, 11:47 PMsettings:
jvm:
release: 21
storeParameterNames: true
jdk:
version: 25
distributions: [ zulu, temurin ]suresh
10/22/2026, 11:47 PMThis is the first run of the Kotlin CLI v0.14.0-dev-4523, so we need to download the Kotlin Toolchain.
Please give us a few seconds, subsequent runs will be faster.
Downloading Kotlin Toolchain distribution v0.14.0-dev-4523...
Download complete.
Downloading Kotlin CLI runtime v25.32.21...
Download complete.
Downloading <https://repo1.maven.org/maven2/org/jetbrains/kotlin/kotlin-native-prebuilt/2.5.0-Beta2/kotlin-native-prebuilt-2.5.0-Beta2-macos-aarch64.tar.gz> to /Users/runner/work/kotlin-vipaccess/kotlin-vipaccess/.kotlin/shared-cache/download.cache/b0bc012aaf-kotlin-native-prebuilt-2.5.0-Beta2-macos-aarch64.tar.gz
Downloading <https://github.com/pnpm/pnpm/releases/download/v11.9.0/pnpm-darwin-arm64.tar.gz> to /Users/runner/work/kotlin-vipaccess/kotlin-vipaccess/.kotlin/shared-cache/download.cache/bfff255e35-pnpm-darwin-arm64.tar.gz
Downloading <https://cdn.azul.com/zulu/bin/zulu25.36.205-ca-jdk25.0.4.1-macosx_aarch64.tar.gz> to /Users/runner/work/kotlin-vipaccess/kotlin-vipaccess/.kotlin/shared-cache/download.cache/15bced2243-zulu25.36.205-ca-jdk25.0.4.1-macosx_aarch64.tar.gz
Downloading <https://github.com/adoptium/temurin25-binaries/releases/download/jdk-25.0.5%2B8/OpenJDK25U-jdk_aarch64_mac_hotspot_25.0.5_8.tar.gz> to /Users/runner/work/kotlin-vipaccess/kotlin-vipaccess/.kotlin/shared-cache/download.cache/f8362503fc-OpenJDK25U-jdk_aarch64_mac_hotspot_25.0.5_8.tar.gzsuresh
10/22/2026, 11:48 PMjoffrey
10/23/2026, 7:53 AMsuresh
10/24/2026, 3:39 AMjoffrey
10/24/2026, 9:38 AMtemurin) in your config was a red herring. I'm betting you have some native platforms, and the Temurin 25 download is just the default JDK 25 used to run the native compiler. If you change your config, say to version 28 and distros [zulu, corretto], your first download will be zulu 28, but the second will still be Temurin 25.joffrey
10/24/2026, 10:02 AMjoffrey
10/24/2026, 10:09 AMJAVA_HOME was set to some JDK 25.
We could make this system smarter by actually looking at already downloaded JDKs outside of JAVA_HOME, maybe keeping some sort of registry, and make this affect the choice of JDK, but this would introduce non-determinism based on which provisioning runs first, so it's a trade-off on reproducibility. That would be a no-go: unlike JAVA_HOME, which is an input of the build, the variability here would be introduced based on races, which would break caching.
We could instead look at the entire project configuration, and see if some module's JDK criteria is a subset of the default JDK criteria. That would be more deterministic, but still quite surprising to users (why does a change in one module affect a completely unrelated module?).joffrey
10/24/2026, 10:10 AM