[
https://issues.apache.org/jira/browse/SLING-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293623#comment-17293623
]
Oliver Lietz commented on SLING-10155:
--------------------------------------
[~enorman], I'm only aware of scripting engines from Sling project itself which
are available for two "major" language versions. You could configure the names
of Groovy and Thymeleaf scripting engines but I don't see a reason to install
multiple engines of those in parallel – not a blocker for me.
> add configuration to include or exclude specific ScriptEngineFactory
> --------------------------------------------------------------------
>
> Key: SLING-10155
> URL: https://issues.apache.org/jira/browse/SLING-10155
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Scripting Core 2.3.6
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Sometimes it may be useful to exclude a ScriptEngineFactory from being used
> by the SlingScriptEngineManager
> One such consideration is excluding the nashorn script engine so it can't be
> used now that it is deprecated.
> You may see messages like this logged to the console when running sling with
> java 11:
> {code:java}
> Warning: Nashorn engine is planned to be removed from a future JDK
> release{code}
> Excluding nashorn via configuration would get rid of those log warnings and
> prevent you from accidentally using it.
> There may be other use cases where a ScriptEngineFactory is available in the
> runtime but not intended for usage with sling so the solution should not be
> "nashorn" specific.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
