On Wed, 19 Mar 2025 12:45:23 GMT, Erik Joelsson <er...@openjdk.org> wrote:
> Just to make sure I'm understanding you correctly. Are you proposing that > instead of building a single JDK distribution with multiple JVMs, they would > build a separate JDK for each alternative JVM configuration and publish > java.base.jmod from each of them for end users to pick from when generating > their run-images? I think there is a compelling case for having a release + fastdebug build of a server libjvm in the same run-time image. I'm dubious about server + minimal in the same run-time image, it's just too weird unless users of minimal VM are also running with `--limit-modules` to use a reduced set of modules before running `jlink` to create the target run-time image for the small environment. For embedded environments then it could be compelling to have the the packaged modules (JMOD files, and not just java.base) published for several OS/architectures. There's a connection to cross building here. Once you have the packaged modules then someone could run `jlink` (on a main-stream platform) to produce the run-time containing the small set of modules that are appropriate for the target environment. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24063#issuecomment-2739578163
