[
https://issues.apache.org/jira/browse/SLING-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406192#comment-16406192
]
Bertrand Delacretaz commented on SLING-7545:
--------------------------------------------
I think this commit fixes this:
https://github.com/apache/sling-org-apache-sling-scripting-core/commit/7f6145e79666c49844c49e9ce0d49d7954713a88
For some reason the {{SlingScriptEngineManager}} was not registered as a
{{BundleListener}} anymore but that's needed to correctly handle scripting
bundles like {{groovy-all.jar}}.
[~fortuna] could you try with this fix? You'll need to build the master branch
of https://github.com/apache/sling-org-apache-sling-scripting-core for that.
> Groovy Scripting Engine not loading in Apache Sling 10
> ------------------------------------------------------
>
> Key: SLING-7545
> URL: https://issues.apache.org/jira/browse/SLING-7545
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Core 2.0.54
> Reporter: Ben Fortuna
> Priority: Major
>
> With the latest release of Apache Sling (10) the Groovy Scripting engine is
> no longer loading.
> The impact is that scripts with a (*.groovy) extension aren't rendering.
> This works with Apache Sling 9, so I believe there was a change in the Apache
> Sling Scripting Core that broke the Groovy implementation.
>
> How to reproduce:
> Load groovy-all JAR into Apache Sling as a bundle, under the url
> [http://localhost:8080/system/console/status-slingscripting] the following
> should display:
> {code:java}
> Groovy Scripting Engine 2.0
> -------------------------------------
> - Language : Groovy, 2.4.14
> - Extensions : groovy
> - MIME Types : application/x-groovy
> - Names : groovy, Groovy{code}
>
> This works with Apache Sling 9, not with Sling 10
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
