Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - ScriptTagger and JDK 17 #118

Open
danizen opened this issue Jul 13, 2022 · 1 comment
Open

Question - ScriptTagger and JDK 17 #118

danizen opened this issue Jul 13, 2022 · 1 comment
Labels

Comments

@danizen
Copy link

danizen commented Jul 13, 2022

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!

@essiembre
Copy link
Contributor

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.

See: https://github.com/openjdk/nashorn

Share your experience if you get a chance to try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants