Nashorn on the module-path

[Hannes Wallnöfer]

Hi Christian,

I cloned and tried your example project. When I run the project, I get one successful and one aborted tests in both cases:

Module path output:

└─ JUnit Jupiter ✔
   └─ CheckTests ✔
      ├─ test() ✔
      └─ emitStringRepresentationOfTestModule() ■ Assumption failed: module check

Class path output:

└─ JUnit Jupiter ✔
   └─ CheckTests ✔
      ├─ test() ✔
      └─ emitStringRepresentationOfTestModule() ■ Assumption failed: unnamed module @306f16f3


Unfortunately it’s quite hard for me to understand what’s going on from there. Your Main class is quite complex with over 800 lines of code, and it seems like the interesting code is in junit-jupiter, which is included in binary form only.

Do you think it’s possible to reduce the problem further, ideally to a plain java class?


Hannes


> Am 27.05.2019 um 11:40 schrieb Christian Stein <sormuras at gmail.com>:
> 
> On Mon, May 27, 2019 at 11:37 AM Sundararajan Athijegannathan <
> sundararajan.athijegannathan at oracle.com> wrote:
> 
>> How can this be reproduced at out end?
> 
> 
> I compiled a small example project at [1] that describes and
> demonstrates the issue. Please view the README.md file for
> details.
> 
> You may reproduce the issue by launching `jshell build.jsh`
> within the root directory of the project -- having JDK 11+ installed.
> 
> [1] https://github.com/sormuras/junit5-class-vs-module-path