IMO, the real question is "should automatic modules see classes from the classpath" ?
if the answer is yes, then they can not be used with jlink. Rémi ----- Mail original ----- > De: "Alan Bateman" <alan.bate...@oracle.com> > À: "Sander Mak" <sander....@luminis.eu>, "jigsaw-dev" > <jigsaw-dev@openjdk.java.net> > Envoyé: Vendredi 4 Mars 2016 09:10:58 > Objet: Re: jlink and automatic modules > > > > On 03/03/2016 16:04, Sander Mak wrote: > > : > > Thanks, that explains it. > > > > The difference in behavior between the two modulepaths threw me off for a > > bit. Whether it's the right thing to do almost sounds more like a > > philosophical rather than a technical discussion? > > > Automatic modules are for migration and so may have references to types > on the class path. If an automatic module is linked into a run-time > image then it could result in dangling references or maybe a DOA > run-time image unless used with -cp. The other thing is the optimizers > and transformers that execute at link-time as they wouldn't have a > "whole world" view. I think these are the main areas that need to be > pondered before deciding whether to allow this or not. > > -Alan >
