OpenJDK 10 and Oracle JDK10 doesn't have the same default modules

[Christian Stein]

I solved the issue by also adding "ALL-DEFAULT" to the "--add-module"
option.
Now both JDK runtimes are happily executing JUnit 5 tests on the module
path.


java
--module-path
  bin/bach/target/classes/test:bin/bach/modules
--add-modules
  ALL-MODULE-PATH,ALL-DEFAULT
--module
  org.junit.platform.console
--scan-modules


https://travis-ci.org/sormuras/beautiful_logger/builds/337224349

Hoping, that we soon my switch to explicit module descriptors. Perhaps
using MR-JARs.

Thanks for the help, Alan!

Cheers,
Christian

On Sun, Feb 4, 2018 at 2:39 PM, Alan Bateman <Alan.Bateman at oracle.com>
wrote:

> On 04/02/2018 12:45, Christian Stein wrote:
>
> :
>
> It's an automatic module. And it does run "as-is" on Oracle JDK,
> using ALL-MODULE-PATH.
>
> Here is the actual command:
>
> java
> --module-path
>   bin/bach/target/classes/test:bin/bach/modules
> --add-modules
>   ALL-MODULE-PATH
> --module
>   org.junit.platform.console
> --scan-modules
>
>
> Perhaps the interpretation of " ALL-MODULE-PATH " by Oracle JDK is too
> generous, as it add all system modules as well?
>
> No, there is no difference there. The main difference between Oracle JDK
> and OpenJDK builds is that the Oracle JDK builds have additional modules
> and specifically the modules for the Java Plugin, Java Web Start, and the
> the JavaFX modules from the OpenJFX project. If you diff the `java
> --list-modules` output from both builds then you'll see the list of
> additional modules.
>
> I suspect this issue is nothing to do with `--add-modules
> ALL-MODULE-PATH`. Instead it's probably one of the JavaFX modules that
> `requires java.scripting`. You should be able to diagnose this quickly by
> running with `--show-module-resolution` and grep the output for
> "java.scripting".
>
> -Alan
>