Project

General

Profile

Actions
Copy link

Bug #15661

closed

Bug #14822: Remove warning: "Nashorn engine is planned to be removed from a future JDK release "

Manage nashorn warning parameter from code

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

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
System integration
Target version:
5.0.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

In #15652, we tried to remove the warning with the correspond JVM parameter. But nashorn is stupid, and if it gets a non recognized parameter, in place of logging that fact (or ignoring it), it crashes. So for openjdk JVM < 11, we weren't able to start the JS engine.

So, we will manage the property at starttime once and for all.

Actions
Copy link
 #1

Updated by François ARMAND about 5 years ago

  • Target version set to 5.0.13
Actions
Copy link
 #2

Updated by François ARMAND about 5 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/2447
Actions
Copy link
 #3

Updated by François ARMAND about 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #4

Updated by François ARMAND about 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Name check changed from To do to Reviewed
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.13 which was released today.

Actions
Copy link

Also available in: Atom PDF