You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2022/06/19 00:23:00 UTC
[jira] [Updated] (SLING-11398) handle serviceloader ScriptEngineFactory defined in a fragment bundle
[ https://issues.apache.org/jira/browse/SLING-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman updated SLING-11398:
--------------------------------
Summary: handle serviceloader ScriptEngineFactory defined in a fragment bundle (was: handle ScriptEngineFactory defined in a fragment bundle)
> handle serviceloader ScriptEngineFactory defined in a fragment bundle
> ---------------------------------------------------------------------
>
> Key: SLING-11398
> URL: https://issues.apache.org/jira/browse/SLING-11398
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Scripting Core 2.4.10
>
>
> Handle loading of ScriptEngineFactory service loader (/META-INF/services/javax.script.ScriptEngineFactory) files that exist in a fragment.
> For example, consider the groovy ScriptEngine included in the starter that has these:
> Host Bundle - org.codehaus.groovy:groovy:3.0.9
> Fragment - org.codehaus.groovy:groovy-jsr223:3.0.9
>
> Expected:
> The groovy ScriptEngineFactory declared in the groovy-jsr223 fragment should be discovered and made available.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)