[ https://issues.apache.org/jira/browse/SLING-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557143#comment-17557143 ]
Eric Norman commented on SLING-11398: ------------------------------------- [~olli] Updated the comment at: [14d248e|https://github.com/apache/sling-org-apache-sling-scripting-core/pull/18/commits/14d248e71ba4ad94c752d666b72b7c4af9ac8f53] Any other concerns that would block moving forward? > 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)