On Fri, 18 Sep 2026 14:36:11 GMT, Alan Bateman <[email protected]> wrote:
>> OK. So what about the following ? >> >> 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. >> For cross-platform linking, the specified module path must contain all >> target-platform >> modules required to create the image, including java.base. > > This is quite good but it will need to expanded to say what the default > module path is. I tried to include above but needs words smithing. 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? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32926#discussion_r4060574462
