You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Scott Murphy (JIRA)" <ji...@apache.org> on 2010/04/29 01:51:54 UTC
[jira] Commented: (SLING-1511) CLONE -Make Scala Scripting JSR 223
compliant
[ https://issues.apache.org/jira/browse/SLING-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862003#action_12862003 ]
Scott Murphy commented on SLING-1511:
-------------------------------------
If I package the script engine like done in the jsr223-engines examples release, I am unable to run jrunscript on the engine.
{code}
/Users/sdmurphy/Desktop/scripts/jsr223-engines/scala-sling/bin
air:bin sdmurphy$ jrunscript -cp ../build/org.apache.sling.scripting.scala.script-0.9.0-SNAPSHOT.jar:../lib/scala-compiler-2.7.7.jar:../lib/scala-library-2.7.7.jar:../lib/slf4j-api-1.5.2.jar:../lib/slf4j-simple-1.5.2.jar -l scala $*
scala> println("hello")
script error: Error executing script
scala>
{code}
> 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.