On Mon, Sep 11, 2017 at 2:21 PM, Alan Bateman <alan.bate...@oracle.com> wrote:
> [...] > > You can also use `--show-module-resolution` to get traces at startup and > satisfied yourself that it working correctly. Using the symbolic constant `--add-modules ALL-MODULE-PATH` works even better when scanning module contents for test classes. See [1] for a proof-of-concept implementation that ship with JUnit 5.1... Cheers, Christian [1] https://github.com/junit-team/junit5/pull/1057#issuecomment-328806352
