[
https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576902#action_12576902
]
Felix Meschberger commented on SLING-315:
-----------------------------------------
> URL
Yes, I now have it (was not available yet in the archives upon my post):
https://scripting.dev.java.net/servlets/ReadMsg?list=dev&msgNo=55
> Groovy people for ScriptEngine
The ScriptEngine does not come from the Groovy people but from
scripting.dev.java.net. Therefore I posted my question there. In fact, they
provide a whole range of ScriptEngine implementations. So, if they would deploy
to a public maven repository, we could almost immediately make use of these.
> Licensing
I agree, that licenses for use are not an issue, neither for Groovy itself nor
for the ScriptEngine implementation from dev.java.net which seems BSD-like. The
problem regarding licensing I have is putting a binary of dev.java.net into the
Apache SVN.
> Groovy support
> --------------
>
> Key: SLING-315
> URL: https://issues.apache.org/jira/browse/SLING-315
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Affects Versions: 2.0.0
> Environment: all
> Reporter: Christian Sprecher
> Priority: Minor
> Attachments: diff.txt, groovy-engine-1.0.jar, groovy.tar.gz
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Implement Groovy as an option for scripting language support. A patch with a
> possible implementation will be attached
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
