Hi Rémi,
Le dim. 10 juil. 2016 à 23:41, Remi Forax a écrit :
> Hi Antoine,
> you were sleeping during my presentation at last Devoxx FR :)
>
I was probably giving mine ;).
The issue is that an automatic jar can access to the classpath while a
> modular jar can not,
> so if jlink allows automat
On 10/07/2016 22:41, Remi Forax wrote:
Hi Antoine,
you were sleeping during my presentation at last Devoxx FR :)
The issue is that an automatic jar can access to the classpath while a modular
jar can not,
so if jlink allows automatic modules, you may have surprising
NoClassDefNotError at runt
Should this be considered a hack? If you have a nexus repository, for
example, you couldn't realistically do that solution with existing jars.
First, there are too many. Second, and more importantly, you wouldn't want
to change the binaries to add module-info.class because it will change the
calcul
Hi Antoine,
you were sleeping during my presentation at last Devoxx FR :)
The issue is that an automatic jar can access to the classpath while a modular
jar can not,
so if jlink allows automatic modules, you may have surprising
NoClassDefNotError at runtime ruining the whole idea of jigsaw.
A s
