Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Download JMODs separately for JDK 24 and later - #2

Open
dkocher wants to merge 1 commit into
mainfrom
issues/1
Open

Download JMODs separately for JDK 24 and later#2
dkocher wants to merge 1 commit into
mainfrom
issues/1

Conversation

@dkocher

@dkocher dkocher commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

Fixes #1.

Since JDK 24, Temurin no longer ships the jmods folder in the JDK (JEP 493). jlink --add-modules ALL-MODULE-PATH then fails with --module-path option must be specified.

Changes

  • New Download JMODs step: if the extracted JDK has no Contents/Home/jmods, download the JMODs archive for the same release and architecture from the Adoptium API into ./<arch>/jmods. It is cached together with the JDK.
  • jlink is called with --module-path, using the bundled JMODs (before JDK 24) or the downloaded ones (JDK 24 and later). The resulting runtime still contains all modules.

Testing

Not run yet. After merging, run the workflow with jdk-25.0.3+9, which failed in run 28674987037. The workflow can also be dispatched against this branch first:

gh workflow run build.yml -R iterate-ch/universal-macos-java-runtime --ref issues/1 -f release=jdk-25.0.3+9

JMODs archives exist for jdk-25.0.3+9 and jdk-25.0.4.1+1. The Adoptium API returns 404 for jdk-24.0.1+9.

Temurin no longer ships the jmods folder in the JDK (JEP 493), which jlink requires with --add-modules ALL-MODULE-PATH. Fix #1.
@dkocher
dkocher requested a review from ylangisc September 13, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build error for add-modules ALL-MODULE-PATH option

1 participant