[
https://issues.apache.org/jira/browse/SLING-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291181#comment-17291181
]
Eric Norman commented on SLING-10155:
-------------------------------------
[~olli] I couldn't say with any certainty why someone would install a script
engine. Perhaps they need a specific script engine for some other use case
within the runtime and don't want that script engine exposed for sling
scripting. Or sometimes people do other strange stuff that I have no control
over.
This solution is simply matching against the "short name" list provided by the
ScriptEngineFactory so if Groovy 2.x and Groovy 3.x contain some unique "short
name" in their list then a regex could select one or the other. If they don't
have something unique then this solution wound not work for that.
> 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
> 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)
