New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine (original) (raw)

Johan Vos johan.vos at gluonhq.com
Thu Jun 7 08:56:57 UTC 2018

I agree with Ben.

If there is enough interest for a particular technology, the community will pick it up, and with the help of Oracle (engineering and non-engineering) make sure it can be continued.

The same happened with JavaFX. I'm almost certain the JavaFX 11 modules will be in Maven Central by 2018-09-25 (java -version). There was enough community interest, so it happened (outside the core OpenJDK release).

On Thu, Jun 7, 2018 at 10:49 AM Ben Evans <benjamin.john.evans at gmail.com> wrote:

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> 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: >> >> http://openjdk.java.net/jeps/335 >> >> - Mark >

More information about the jdk-dev mailing list