On Tue, 22 Sep 2026 07:04:49 GMT, Dušan Bálek <[email protected]> wrote:
>> OK. Here is another update: >> >> A ":"-separated list of elements, each of which is a file path to a module >> or a directory >> containing modules. Each module is either a modular JAR file, a JMOD file, or >> an exploded-module directory. >> If the specified module path does not contain java.base, it is prepended to >> the default module path. The default module path contains the standard and >> JDK >> modules of the JDK running jlink. >> For cross-platform linking, the specified module path must contain all >> target-platform >> modules required to create the image, including java.base. >> >> What do you think? > > It seems there are no objections, so I’ve updated the PR with the new text. For the man page then I think the second paragraph should be expanded to include "This allows `jlink` to find `java.base` and other modules without specifying their locations to the `--module-path` option. If the `--module-path` option is not specified, then only the default module path is used." I don't think paragraph 3 can use "cross-platform linking" as it's not described anywhere. Can you try this instead "When creating a run-time image for a different target platform (cross-linking), the specified module path must contain all modules required for the target platform, including `java.base`." ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32926#discussion_r4069194811
