New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine

[Luigi Dell'Aquila]

To answer Johan and Ben,

OrientDB is released as a bundle, compatible with Java8, with Apache2
license, if Nashorn is separately released with GPL license we won't be
able to use it.
Moreover, it is distributed as a binary package and it is compatible with
Java 8, so we should see how to bundle Nashorn in the distribution without
creating conflicts with the classpath in Java 8.

Thanks

Luigi




2018-06-07 10:48 GMT+02:00 Mario Ivankovits <mario at datenwort.at>:

> 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,
> Mario
>
>
>
> Am 07.06.2018 um 10:39 schrieb Ben Evans <benjamin.john.evans at gmail.com
> <mailto:benjamin.john.evans at gmail.com>>:
>
> 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?
>
> Thanks,
>
> Ben
>
> On Thu, Jun 7, 2018 at 10:28 AM, Mario Ivankovits <mario at datenwort.at
> <mailto:mario at datenwort.at>> wrote:
> Hi!
>
> 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,
> Mario
>
>
> Am 06.06.2018 um 20:16 schrieb mark.reinhold at oracle.com<mailto:
> mark.reinhold at oracle.com>:
>
> http://openjdk.java.net/jeps/335
>
> - Mark
>
>
>