[
https://issues.apache.org/jira/browse/SLING-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862141#action_12862141
]
Michael Dürig commented on SLING-1511:
--------------------------------------
The Scala scripting engine [1] *is* independent from Sling already. It just
still lives within Sling. Ultimately it should move to a better home though [2].
The support material of my session at Scala Days 2010 [3] contains some demo
code which shows how to use the Scala script engine in standalone mode.
For configuring the script engine (i.e. setting a custom classpath) see
org.apache.sling.scripting.scala.config.AbstractSettingsProvider.
NB: Please use the mailing list for questions [4] next time.
[1] http://svn.apache.org/viewvc/sling/trunk/contrib/scripting/scala/script/
[2]
http://dev.day.com/discussion-groups/content/lists/sling-dev/2009-12/2009-12-01_Scala_scripting_support_was_Re_And_another_one____Michael_D_rig.html
[3] http://people.apache.org/~mduerig/scala4scripting/
[4] http://mail-archives.apache.org/mod_mbox/sling-users/
> CLONE -Make Scala Scripting JSR 223 compliant
> ---------------------------------------------
>
> Key: SLING-1511
> URL: https://issues.apache.org/jira/browse/SLING-1511
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Scott Murphy
> Assignee: Carsten Ziegeler
> Priority: Minor
>
> As discussed [1] it would be nice if we could decouple the Scala scripting
> engine from Sling making it into a independent JSR 223 compliant script
> engine which is 'just' used by Sling.
> [1] http://markmail.org/message/mkvjbuk5dfrekvqv?q=scala+another+sling
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
