If users don't follow best practices, then yes (If Controller and While Controller use Javascript so nashorn). But if we switch to rhino as default JS engine, it should work in 99% of cases.
If it's overkill, maybe it's not worth investing in this. Noting that IMO, JS is bad for JMeter performances. The best thing would be to make IfController / While Controller use JEXL3 by default instead of JS, but how to manage transition in a clear way ? Regards On Wed, Mar 25, 2020 at 6:37 PM sebb <[email protected]> wrote: > Is Nashorn or its replacment needed for *all* test plans? > If not, then another alternative is to document how to download it, > and report a suitable error if a test plan needs it. > > On Mon, 23 Mar 2020 at 17:57, Felix Schumacher > <[email protected]> wrote: > > > > The third option would be to go back to rhino, which is included in > jmeter anyhow. > > > > Wouldn't it? > > > > Felix > > > > Am 23. März 2020 16:59:43 MEZ schrieb Vladimir Sitnikov < > [email protected]>: > > >up. > > > > > >Graal.JS seems to be mature now. > > >It can run on any Java machine: > > > > https://github.com/graalvm/graaljs/blob/master/docs/user/RunOnJDK.md#run-graalvm-javascript-on-a-stock-jdk > > > > > >The licenses there are MIT and/or UPL (both are permissible for Apache) > > > > > >The sad thing is that Graal.JS is ~20 megabytes extra. > > > > > > > > >It is extremely likely Nashorn will be removed from Java 15, so we need > > >to > > >deal with it somehow. > > > > > >So the options are: > > >a) Bundle Graal.JS (+20MiB :( ) > > >b) Document the way to add Graal.JS jars as an external dependency > > >(everybody would need to download the file manually :( ) > > >c) Add an option to download Graal.JS on demand (not that trivial to > > >implement, yet useful for many(!) other cases) > > > > > >WDYT? > > > > > >Vladimir > -- Cordialement. Philippe Mouawad.
