On Fri, 18 Sep 2026 14:30:10 GMT, Dušan Bálek <[email protected]> wrote:
>> The module path specified to jlink is `--module-path` is prepended to its >> default module path. I think we should just describe that and not use words >> like "external" as it too different to how we document the module path in >> the other tools, API docs, and JEPs. > > 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. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32926#discussion_r4047694151
