You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Ben Fortuna (JIRA)" <ji...@apache.org> on 2018/03/17 12:09:00 UTC
[jira] [Commented] (GROOVY-8513) Groovy Scripting Engine not
loading in Apache Sling 10
[ https://issues.apache.org/jira/browse/GROOVY-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403401#comment-16403401 ]
Ben Fortuna commented on GROOVY-8513:
-------------------------------------
I've created an issue in the Apache Sling Jira as I think the problem stems from a code change in the scripting core library
> Groovy Scripting Engine not loading in Apache Sling 10
> ------------------------------------------------------
>
> Key: GROOVY-8513
> URL: https://issues.apache.org/jira/browse/GROOVY-8513
> Project: Groovy
> Issue Type: Bug
> Components: Groovlet / GSP
> Affects Versions: 2.4.14
> 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)