> Have you brought this up on nashorn-dev... No, but cc-ed that list now.
> ...as this might require digging into the dynalink linker > and how method handles are used. Do you think it's still worth the effort in regard of Nashorn being deprecated for removal? Perhaps the underlying reason may show up on/in a different module, soon. Said that, the JUnit 5 team decided to remove "script- based conditions" from Jupiter. So, "we" won't be affected by this issue in the near future anymore. [1] https://github.com/junit-team/junit5/issues/1882 On Sun, May 26, 2019 at 10:35 AM Alan Bateman <alan.bate...@oracle.com> wrote: > On 16/05/2019 15:02, Christian Stein wrote: > > : > > It didn't emit any new line. Is there another debug switch I can enable? > > Have you brought this up on nashorn-dev as this might require digging into > the dynalink linker and how method handles are used. > > -Alan >
