New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine

Mario Ivankovits mario at
Thu Jun 7 08:48:23 UTC 2018

Well, I don’t wanted to express any concern.
It is just, in den JEP they write:

"The breadth of Nashorn usage has not been easy to track. It is hoped that feedback for this JEP might provide better insight into actual Nashorn usage."

… and that is what happens now. We give feedback.

I am fine with whatever solution we might come up.

Best regards,

Am 07.06.2018 um 10:39 schrieb Ben Evans <benjamin.john.evans at<mailto:benjamin.john.evans at>>:

I don't really understand the concern here - presumably the modules
will simply be removed from core, and the community will be at liberty
to change the module name and re-release the Nashorn component as GPL
on Maven Central?

Even in the absence of an Oracle-blessed upgrade path (whether that's
TruffleJS on HotSpot, or a full-blown move to GraalVM), the community
surely always has this option?



On Thu, Jun 7, 2018 at 10:28 AM, Mario Ivankovits <mario at<mailto:mario at>> wrote:

We too use it in our application to allow to configure highly non-standard processes which is not easy to build a configuration for and also not worth to clutter the codebase.
Just very small code snippets, but still ...

Best regards,

Am 06.06.2018 um 20:16 schrieb mark.reinhold at<mailto:mark.reinhold at>:

- Mark

More information about the jdk-dev mailing list