mp;t=2570
> (in french)
>
Thanks for the trick, I'm not a big fan of updating released jar, but it's
better than nothing.
Antoine
>
> Rémi
>
> - Mail original -
> > De: "Antoine Sabot-Durand"
> > À: jigsaw-dev@openjdk.java.net
> > En
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
gt; Rémi
>
> - Mail original -
> > De: "Antoine Sabot-Durand"
> > À: jigsaw-dev@openjdk.java.net
> > Envoyé: Dimanche 10 Juillet 2016 22:40:57
> > Objet: Jlink and automatic module
> >
> > Hi All,
> >
> > I encounter the sam
e: "Antoine Sabot-Durand"
> À: jigsaw-dev@openjdk.java.net
> Envoyé: Dimanche 10 Juillet 2016 22:40:57
> Objet: Jlink and automatic module
>
> Hi All,
>
> I encounter the same problem than Sander in [1] regarding automatic modules
> and Jlink.
> My project has
Hi All,
I encounter the same problem than Sander in [1] regarding automatic modules
and Jlink.
My project has a lot of modules and uses a lot of dependencies (Java EE
spec and impls) so it took me a few days to walk thru the writing of all my
module-info.java files. hopefully I only found 2 automa
