[
https://issues.apache.org/jira/browse/SLING-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557099#comment-17557099
]
Oliver Lietz commented on SLING-11398:
--------------------------------------
{quote}Well, the test is specifically for testing a factory declared in a
fragment per the comment at the top of the test class. The 3.0.1 version works
if you remove the ".noStart()" statement that keeps it from trying to start the
fragment bundle. But that is not the point of this test.
{quote}
Sure, but it's not obvious to everyone that additional Groovy artifacts were
sometimes released as regular bundles and sometimes as fragments. So we should
have a clear statement that a fragment is required here.
> 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
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
