RFR: 8311302: Allow for jlinking a custom runtime without packaged modules being present [v20]

[Mandy Chung]

On Mon, 18 Mar 2024 13:01:10 GMT, Severin Gehwolf <sgehwolf at openjdk.org> wrote:

> Yes we do. The main reason being that the `jdk` image has more to it than just the image. `src.zip`, CDS data, `demo` and so on. We don't want to duplicate that. To us, including the `jmods` folder is something that comes into play when actually producing the bundles of the JDK. The linkable runtime option allows for a more flexible distribution of the resulting JDK. With or without packaged modules without limiting `jlink` usage (for the common use-cases).

I'm not sure how keeping packaged modules is related to `src.zip`, CDS data, `demo` and so on as they are the targets after `images/jdk` is built.

However, I got your point that users should configure what they want the JDK image to produce as a linkable runtime image and packaged modules are orthogonal.   Okay with me.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/14787#issuecomment-2004605507