[jira] [Resolved] (SLING-10155) add configuration to include or exclude specific ScriptEngineFactory

["Eric Norman (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Norman resolved SLING-10155.
---------------------------------
    Resolution: Fixed

Feedback from the reviews has been integrated and no objections remain, so I have merged the PR at: https://github.com/apache/sling-org-apache-sling-scripting-core/commit/3d910d1624c940b390e9163c24b6ffaa24287262

> 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: 4h 10m
>  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)