#CompileTimeDependencies and module resolution

Remi Forax forax at univ-mlv.fr
Fri Jan 13 14:57:13 UTC 2017

Ok, thanks.


----- Mail original -----
> De: "Sander Mak" <sander.mak at luminis.eu>
> À: "jigsaw-dev" <jigsaw-dev at openjdk.java.net>
> Envoyé: Vendredi 13 Janvier 2017 14:47:59
> Objet: Re: #CompileTimeDependencies and module resolution

> On 13 Jan 2017, at 14:37, forax at univ-mlv.fr<mailto:forax at univ-mlv.fr> wrote:
> As i've read the mail of Sander,
> the module which is required statically is present in the module path but not
> resolved by default, you have to use --add-modules. But maybe i'm wrong ?
> You're not wrong, see the email exchange with Stephen as well. Just a `requires
> static` does not cause a module to be resolved from the module path, there
> needs to be a non-static requires or --add-modules for the optional module.
> This is intentional behaviour according to the proposal:
> http://mail.openjdk.java.net/pipermail/jpms-spec-experts/2016-June/000306.html
> Sander

More information about the jigsaw-dev mailing list