You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2018/03/20 11:41:00 UTC

[jira] [Updated] (SLING-7545) Groovy Scripting Engine not loading in Apache Sling 10

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

Bertrand Delacretaz updated SLING-7545:
---------------------------------------
    Fix Version/s: Scripting Core 2.0.56

> 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
>             Fix For: Scripting Core 2.0.56
>
>
> 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)