P4
A DESCRIPTION OF THE REQUEST :
When building a 32-bit JVM, jlink includes both the Client and Server VMs in the output. This is wasteful since any particular packaged application will typically use only one or the other. A "minimal" JVM with options "--strip-debug --compress=2 --addmods java.base" is 21 MB. Despite all the work put into the module system and the fancy compression that jlink does, one third of that output is completely superfluous if you don't know about or use the Server VM. I figured out that it can be stripped manually by deleting "bin/server", "lib/server", and the "-server KNOWN" entry from "lib/i386/jvm.cfg", but this would be easier and much more discoverable if there were a command-line option to choose exactly which VM(s) to include.
JUSTIFICATION :
.
When building a 32-bit JVM, jlink includes both the Client and Server VMs in the output. This is wasteful since any particular packaged application will typically use only one or the other. A "minimal" JVM with options "--strip-debug --compress=2 --addmods java.base" is 21 MB. Despite all the work put into the module system and the fancy compression that jlink does, one third of that output is completely superfluous if you don't know about or use the Server VM. I figured out that it can be stripped manually by deleting "bin/server", "lib/server", and the "-server KNOWN" entry from "lib/i386/jvm.cfg", but this would be easier and much more discoverable if there were a command-line option to choose exactly which VM(s) to include.
JUSTIFICATION :
.