Project

General

Profile

Actions

Bug #14753

closed

Warning: Nashorn engine is planned to be removed from a future JDK release

Added by François ARMAND over 5 years ago. Updated about 3 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Large
Priority:
18
Name check:
Fix check:
Regression:

Description

UPDATE: as of JDK15, nashorn is removed.

GraalJS seems the best solution:
- it can run on openjdk as a simple lib dep: https://github.com/graalvm/graaljs/blob/master/docs/user/RunOnJDK.md
- it has nashorn compatible mode: https://github.com/graalvm/graaljs/blob/master/docs/user/ScriptEngine.md

Security will need to be updated.

===

Since OpenJDK 11, we get a warning: "Warning: Nashorn engine is planned to be removed from a future JDK release".

The fact that nashorn will be removed is terrible, and we will need to address that. Some reference links seems to tell that we will need to switch to GraalVM at some point:

junit-team/junit5#1481
https://openjdk.java.net/jeps/335
https://jaxenter.com/nashorn-javascript-engine-deprecated-145320.html
https://www.infoworld.com/article/3291322/javascript/oracle-switch-now-from-nashorn-javascript-engine-to-graalvm.html
https://medium.com/graalvm/oracle-graalvm-announces-support-for-nashorn-migration-c04810d75c1f

In the meantime, we get a bad, red error message at startup, and we should really hide it, because rudder user really don't care about that. We need to add at startup options:

-Dnashorn.args="--no-deprecation-warning" 

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #14822: Remove warning: "Nashorn engine is planned to be removed from a future JDK release " ReleasedBenoît PECCATTEActions
Related to Rudder - Bug #18214: Document that JDK 15 is not supported because of nashorn removingReleasedAlexis MoussetActions
Actions #1

Updated by François ARMAND over 5 years ago

  • Target version changed from 5.0.10 to Ideas (not version specific)

I'm setting that one as "no idea when we will have to do it", and I'm opening an other for the warning.

Actions #2

Updated by François ARMAND over 5 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Large
  • Priority changed from 0 to 22
Actions #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Related to Bug #14822: Remove warning: "Nashorn engine is planned to be removed from a future JDK release " added
Actions #4

Updated by François ARMAND about 4 years ago

  • Related to Bug #18214: Document that JDK 15 is not supported because of nashorn removing added
Actions #5

Updated by François ARMAND about 4 years ago

  • Description updated (diff)
  • Priority changed from 22 to 18
Actions #6

Updated by François ARMAND about 4 years ago

  • Description updated (diff)
Actions #7

Updated by François ARMAND over 3 years ago

  • Target version changed from Ideas (not version specific) to 7.0.0~beta1
  • Priority changed from 18 to 9
Actions #8

Updated by François ARMAND over 3 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #9

Updated by François ARMAND over 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3623
Actions #10

Updated by François ARMAND over 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #12

Updated by Vincent MEMBRÉ about 3 years ago

  • Status changed from Pending release to Released
  • Priority changed from 9 to 18

This bug has been fixed in Rudder 7.0.0~beta1 which was released today.

Actions

Also available in: Atom PDF