You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JDK 17 deprecates the Nashorn JS engine. My colleague Tracy, who is actively using the product, is not using the script tagger as she is more of a Java programmer than I am. However, I am concerned about what the importer plans to do with regard to the ScriptTagger.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for bringing this to our attention. It turns out Nashorn still exists independently and is reported to work on Java 11 and up. It would have to be manually added to the classpath for now when using Java 17, but it should be auto-discovered when added. This means people should still be able to use JavaScript without problem with Java 17 and hopefully many releases after that.
JDK 17 deprecates the Nashorn JS engine. My colleague Tracy, who is actively using the product, is not using the script tagger as she is more of a Java programmer than I am. However, I am concerned about what the importer plans to do with regard to the ScriptTagger.
Thanks!
The text was updated successfully, but these errors were encountered: