Actions
Bug #15661
closedBug #14822: Remove warning: "Nashorn engine is planned to be removed from a future JDK release "
Manage nashorn warning parameter from code
Pull Request:
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.
Updated by François ARMAND over 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
Updated by François ARMAND over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|7c5ee98d5ddce7e58f7e04aafb6b354b27404058.
Updated by François ARMAND over 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 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