Hi Daniel, several points first, the JRE doesn't exist anymore apart for compatibility (the jre is just a bunch of modules) and a jar can be a modular jar, just have a module-info.class in the jar, so applications that uses jars can be modular, they do not have to use jlink.
So you can have a jlink image as small as just java.base and all your applications and their dependencies as modular jars, the modules will be shared by the different applications, or a jlink all applications and have no sharing at all and all the states in between. Rémi ----- Mail original ----- > De: "Daniel Latrémolière" <daniel.latremoli...@gmail.com> > À: "Alan Bateman" <alan.bate...@oracle.com>, "jigsaw-dev" > <jigsaw-dev@openjdk.java.net> > Envoyé: Jeudi 31 Août 2017 20:47:35 > Objet: Re: Jigsaw and containers >> Are you using `jlink` to create a run-time image for each application? >> (just trying to establish if you are actually running into an issue or >> not). > With jlink per application, all will be working without problems, but > each application will have his own copy of JRE and common libraries (big > size). > > With jlink only for jre and common libraries, these parts can be shared > between applications. But specific parts of each application will be > only in JAR files (and not be modularized). > > These two choices works as reasonable targets, but no one is really > completely good (big size or no full modularization). > > Daniel.
