Repository navigation
Support Temurin JMOD distribution #804
Description
Description:
From JDK24 onwards, Temurin's default distribution does not ship JMODs any more: adoptium/adoptium-support#1271
They are going to provide another download for it: adoptium/adoptium-support#1271 (comment)
There should be an additional option jmod: true/false in the configuration at https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#Eclipse-Temurin
Justification:
Some users want to have JMODs and use Temurin.
Are you willing to submit a PR?
Unfortunately, I have no resources for this.
Activity
v-gowridurgad commentedon Apr 28, 2025
Hi @koppor, Thank you for creating this feature request. We will investigate it and provide feedback as soon as we have some updates.
karussell commentedon May 9, 2025
This is a problem now for normal builds. At least for 25-ea the jmod package is download by default instead of the JDK.
See this build log where it cannot find a java command anymore because it downloads:
https://github.com/adoptium/temurin25-binaries/releases/download/jdk-25%2B21-ea-beta/OpenJDK-jmods_x64_linux_hotspot_25_21-ea.tar.gz
instead of
https://github.com/adoptium/temurin25-binaries/releases/download/jdk-25%2B21-ea-beta/OpenJDK-jdk_x64_linux_hotspot_25_21-ea.tar.gz
The previous build with jdk-25+20 worked fine and we didn't change anything on our side.
Update 12th August 2025: seems to work fine again and uses currently 25.0.0-ea.35.0.ea
build: removed jdk 25-ea until issue is fixed actions/setup-java#804
ilgrosso commentedon May 9, 2025
@karussell I am experiencing the same issue in the last ~24 hours
build: remove jdk-25 from build matrix until upstream issue fix actio…
Switch CI/CD to Corretto
brunoborges commentedon Jul 14, 2026
@gdams this is overly complicated. What is the current status of Temurin? Are JDKs with or without JMOD files? Shouldn't JDKs be shipped with JMODS, and if the user wants a jmod-less JDK, then they download a specific build?
gdams commentedon Jul 20, 2026
adding @jerboaa as I know he helped role this out for Temurin. I think the key thing is that 99% of the time the JDK doesn't actually require the JMOD archives so the decision was made to strip them out and ship them as a separate artefact. There's only a small handful of reasons that a user would actually require the archives.
jerboaa commentedon Jul 20, 2026
Yes, exactly. The default should be the default, build. For Temurin 24+ that is a build without JMODs and JEP 493 enabled. For users who need it, they could request JMODs explicitly.