[
https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576893#action_12576893
]
bdelacretaz edited comment on SLING-315 at 3/10/08 1:24 AM:
--------------------------------------------------------------------
Felix, do you have an URL for the thread on dev (at) scripting.dev.java.net, so
that people can follow the discussion?
We could also ask the Groovy people directly, about releasing the ScriptEngine
in a Maven repository, or do you think that's out of their scope?
The Groovy license if not a problem, I downloaded Groovy 1.5.4 to check and
it's Apache-licensed, and uses http://asm.objectweb.org/ which also uses an
Apache-like license.
was (Author: bdelacretaz):
Felix, do you have an URL for the thread on [EMAIL PROTECTED], so that
people can follow the discussion?
We could also ask the Groovy people directly, about releasing the ScriptEngine
in a Maven repository, or do you think that's out of their scope?
The Groovy license if not a problem, I downloaded Groovy 1.5.4 to check and
it's Apache-licensed, and uses http://asm.objectweb.org/ which also uses an
Apache-like license.
> 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.
