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

[Severin Gehwolf]

On Mon, 3 Jun 2024 12:55:54 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> So I think we may have the wrong default. Yes, they are separate configure and jlink options but I'm wondering if it would be more sensible to opt-in(not opt-out) to keep the packaged modules when configured with --enable-runtime-link-image.

OK. I'll rework it so that we'll have:

| config opts | effect | equivalent to |
| -----------------|----------|---------------------|
| `--enable-runtime-link-image` | produces a linkable runtime **without** packaged modules even though the default of  `--enable-packaged-modules` is otherwise `true`.| `--enable-runtime-link-image --disable-packaged-modules`|
| `--enable-runtime-link-image --enable-packaged-modules`| produces a linkable runtime **with** packaged modules, overriding the default of packaged modules not being enabled when `--enable-runtime-link-image`  is being used otherwise | N/A|
| `--disable-runtime-link-image` | Default as of today. Adds packaged modules, with no run time link supporting jimage | `--disable-runtime-link-image --enable-packaged-modules`|
| `--disable-runtime-link-image --disable-packaged-modules` | No linkable jimage runtime, no packaged modules in the resulting JDK | N/A |

Does that proposal sound good?

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

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