jlink and automatic modules

Alan Bateman Alan.Bateman at oracle.com
Sun Dec 11 11:23:20 UTC 2016

On 10/12/2016 22:40, Claes Redestad wrote:

> The intended behavior is for jlink to operate on any set of modules to
> support linking images for other platforms, operating systems etc (the
> java.base jmod shipped with any JDK contains a native JVM), so it may
> feel more natural to make it explicit all the way rather than design a
> way to exclude and override parts of the module-path.
> I see no obvious technical reason it wouldn't work if someone put their
> mind to it, but it might be a non-trivial effort to get right for
> something that's really only a small quality of life improvement.
Sundar has had one or two proposals on this. As you note, the solution 
needs to take account of cross linking and also the scenario where the 
jlink tool is running on one JDK but is producing a run time image from 
packages modules for a different JDK (say a tool running on 9 but 
producing a run-time image for 9.1).


More information about the jigsaw-dev mailing list