JEP 335: Deprecate the Nashorn JavaScript Engine

OwnerJim Laskey
StatusClosed / Delivered
Componentcore-libs / jdk.nashorn
Discussionjdk dash dev at openjdk dot java dot net
Relates toJEP 372: Remove the Nashorn JavaScript Engine
Reviewed byAlex Buckley, Brian Goetz, Dalibor Topic
Endorsed byMark Reinhold
Created2018/05/08 14:23
Updated2020/04/06 21:21


Deprecate the Nashorn JavaScript script engine and APIs, and the jjs tool, with the intent to remove them in a future release.


The Nashorn JavaScript engine was first incorporated into JDK 8 via JEP 174 as a replacement for the Rhino scripting engine. When it was released, it was a complete implementation of the ECMAScript-262 5.1 standard.

With the rapid pace at which ECMAScript language constructs, along with APIs, are adapted and modified, we have found Nashorn challenging to maintain.


This deprecation does not affect, in any way, the javax.script API.


Two JDK modules will be terminally deprecated, that is, annotated with @Deprecated(forRemoval=true):

A separate JEP will be filed for the actual removal of the types and modules in a future JDK feature release.


An alternative is for a set of credible developers to express a clear desire to maintain Nashorn going forward. If that happens before this JEP is integrated then this JEP can be withdrawn. If that happens after this JEP is integrated, but before Nashorn is removed, then a follow-on JEP can revert the deprecation.

Risks and Assumptions

The risk of removing Nashorn is that certain applications will no longer run because of the expectation that JavaScript is present. 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.