[
https://issues.apache.org/jira/browse/SLING-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated SLING-1274:
---------------------------------
Attachment: SLING-1274.patch
Proposed patch.
This removes the current interpreter and engine module and adds two new
modules: script and config.
The script module contains the Scala scripting engine which is now independent
from Sling. Optimally I think this module should finally move out of Sling into
a new, better suited home. Currently the Scala script engine has an optional
dependency on javax.jcr. Since we alreay had support for running the Scala
compiler of a JCR repository instead of a file system I thought it would be
nice to keep the related utility classes.
The config module is specific to Sling. It parametrizes the Scala script engine
for interoperability with Sling.
To enable Scala scripting for Sling, install the following bundles:
- org.apache.sling:org.apache.sling.scripting.scala.config
- org.apache.sling:org.apache.sling.scripting.scala.script
- org.scala-lang-osgi:scala-compiler
- org.scala-lang-osgi:scala-library
The former two bundles are in this patch. The latter two bundles can be
obtained from http://scala-tools.org/repo-releases/
> Make Scala Scripting JSR 223 compliant
> --------------------------------------
>
> Key: SLING-1274
> URL: https://issues.apache.org/jira/browse/SLING-1274
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Michael Dürig
> Priority: Minor
> Attachments: SLING-1274.patch
>
>
> 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.
