On Thu, 17 Sep 2026 20:08:06 GMT, Pavel Rappo <[email protected]> wrote:
>> Even without JEP 493, there is no guarantee that the run-time image was >> created with `--keep-packaged-modules` so it may not contain the packaged >> modules. >> >> The other thing we need to get across in the description is that the >> "default module path" is appended to the path specified to `--module-path`. >> I need only specify the location of my modules, jlink will find the >> dpeendences in the run-time image if possible. That might be using the >> packaged modules or the run-time image itself. > >> Even without JEP 493, there is no guarantee that the run-time image was >> created with `--keep-packaged-modules` so it may not contain the packaged >> modules. >> >> The other thing we need to get across in the description is that the >> "default module path" is appended to the path specified to `--module-path`. >> I need only specify the location of my modules, jlink will find the >> dpeendences in the run-time image if possible. That might be using the >> packaged modules or the run-time image itself. > > So, in this case, my earlier thought "why mention jmods at all?" seems to > make even more sense, no? So something like this ? If this option is not specified, or if the specified module path does not contain java.base, required JDK modules are obtained from the current JDK. Modules external to the current JDK must always be specified on this path. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32926#discussion_r4044740510
