RFR: 8345259: When linking from the run-time image ALL-MODULE-PATH is not accepted

[Alan Bateman]

On Fri, 6 Dec 2024 09:31:21 GMT, Severin Gehwolf <sgehwolf at openjdk.org> wrote:

> > Just to double check, with the default build, then `jlink --add-modules ALL-MODULE-PATH --output myimage` would fail because the module path hasn't been specified. No difference between default and --generate-linkable-runtime build. It would be a change in behaviour but I think the right thing to do.
> 
> Originally I hadn't intended to do that, but I can add this. Should I do it in this bug or a separate one? I would think that this change of behaviour would need a CSR?

I think this case was missed when jlink was modified to default the module path to $JDK_HOME/jmods. I think my preference would be for this case to fail when --module-path is not specified. Let's see if Mandy agrees. If we do this change then it would be a behavior change so would need a CSR.

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

PR Comment: https://git.openjdk.org/jdk/pull/22494#issuecomment-2522931476