Moving to Java 9 - module-info.class not found for <module-name> module

[Rahman USTA]

Thank you, Remi and Alex.

I think automatic modules can be supported by jlink. It could be a
transition feature like --illegal-access imho.

Kind regards.

2017-09-02 0:59 GMT+03:00 Remi Forax <forax at univ-mlv.fr>:

> As Alex said,
> jackson.databind is not an explicit module.
>
> You should report that issue to their bugtracker.
>
> cheers,
> Rémi
>
> ----- Mail original -----
> > De: "Alex Buckley" <alex.buckley at oracle.com>
> > À: "jigsaw-dev" <jigsaw-dev at openjdk.java.net>
> > Envoyé: Vendredi 1 Septembre 2017 23:06:16
> > Objet: Re: Moving to Java 9 - module-info.class not found for
> <module-name> module
>
> > On 9/1/2017 1:21 PM, Rahman USTA wrote:
> >> java --module-path
> >> %JAVA_HOME%/jmods;target\terminalfx.jar;target\dependency --add-modules
> >> terminalfx -m terminalfx/com.terminalfx.AppStarter
> >
> > (You shouldn't need the --add-modules, since terminalfx is already the
> > main module.)
> >
> >> It works normally. Then, I want to generate a jlink image with the
> >> following script
> >>
> >> jlink --module-path
> >> %JAVA_HOME%/jmods;target\terminalfx.jar;target\dependency --add-modules
> >> terminalfx --launcher terminalfx=terminalfx/com.terminalfx.AppStarter
> >> --output target/release
> >>
> >> However it gives me the following error;
> >>
> >> Error: module-info.class not found for jackson.databind module
> >
> > I suspect jackson.databind is an automatic module. jlink does not
> > support linking of automatic modules because they can rely on the
> > arbitrary content of the classpath, which goes against the idea of a
> > self-contained Java runtime.
> >
> > Alex
>



-- 
Rahman USTA
Istanbul JUG
https://github.com/rahmanusta