You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2008/11/18 13:55:44 UTC
[jira] Commented: (SLING-315) Groovy support
[ https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648585#action_12648585 ]
Paul King commented on SLING-315:
---------------------------------
The groovy all jar should now incorporate this functionality. It should be in the main maven repo in a couple of weeks time when groovy-1.6-rc-1 is released. In the meantime, if you are keen, you can point to the codehaus maven snapshot repo:
http://snapshots.repository.codehaus.org
with this pom info:
{code:xml}
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-all</artifactId>
<version>1.7-beta-1-SNAPSHOT</version>
{code}
Just to summarise: you don't need {{groovy-engine.jar}} anymore. The groovy jar should contain the equivalent functionality and {{META-INF/services}} entry. It should run fine on Java 1.6 or on 1.5 if you supply a backported jsr-223 implementation, e.g. livetribe-jsr223.
Cheers, Paul.
> Groovy support
> --------------
>
> Key: SLING-315
> URL: https://issues.apache.org/jira/browse/SLING-315
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Affects Versions: 3
> 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.