Since initially raising concerns about the move to Java 17 losing Nashorn, I have been investigating the suggestion to use Nashorn as a standalone package as potential easier alternative to GraalVM. [1]
While making some progress, a number of issues have been encountered which I haven't been able to resolve as yet. More details are included in relevant JIRA tickets, but summarising: - Building NiFi with a recent Nashorn dependency leads to errors "Unsupported class file major version 61" [2] - Building NiFi using Java 17 highlights issues with the current Jetty version, which I believe would require an upgrade from 9.4.51 to 11.0.15 [3] - Jetty 11 then requires an upgrade of the Spring Framework version 5 to 6. [4] The current steps to remove references to "Javascript" as a preinstalled scripting language [5] are understandable, but it does seem there is still quite a bit to do before Nashorn or another external scripting engine could be used. [1] https://issues.apache.org/jira/browse/NIFI-11700: Java 17 Nashorn standalone support [2] https://issues.apache.org/jira/browse/NIFI-11701: Support building with version 61 class files [3] https://issues.apache.org/jira/browse/NIFI-11702: Upgrade Jetty to version 11 [4] https://issues.apache.org/jira/browse/NIFI-11703: Upgrade Spring Framework to version 6 [5] https://issues.apache.org/jira/browse/NIFI-11713: Remove Deprecated ECMAScript Support Regards, Dirk Arends
