Scala Script Engine: Move Scala scripting Engine to a more suitable home
------------------------------------------------------------------------
Key: SLING-2038
URL: https://issues.apache.org/jira/browse/SLING-2038
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Michael Dürig
Assignee: Michael Dürig
The Scala scripting engine itself [1] has no dependencies to Sling and almost
none to JCR. Rather can it be used as a standalone JSR 223 compliant scripting
engine. As discussed earlier [2] I think it would be great to give it some more
exposure to the Scala community by moving it to a more appropriate home.
Alex Parvulescu came up with the idea of moving it to
http://scala-tools.org/
There are several way how to host the project then:
1. Like Lift - the web framework the releases are deployed on scala-tools the
source code is on github https://github.com/lift the wiki page is on assembla
https://www.assembla.com/wiki/show/liftweb
2. Like the Scala IDE releases also on scala-tools source on assembla
http://scala-ide.assembla.com/wiki/show/ae55a-oWSr36hpeJe5avMc
3. Like the Scala language releases on scala-tools code on their own servers
http://www.scala-lang.org/node/213
I'd go with github for the sources (it seems everybody is doing that), signup
for an assembla page to keep the docs up to date (github does not seem to have
any wiki options), and contact the scala-tools guys so we can use their maven
repo to deploy artifacts (the alternative would be to go directly to sonatype
and signup, which is very similar but does not have the cool scala like name)
See [3] for some initial discussion
Michael
[1] http://svn.apache.org/viewvc/sling/trunk/contrib/scripting/scala
[2] http://markmail.org/message/mlfs33tkbmayu7ks?q=scala+sling-dev
[3] http://markmail.org/thread/qoxx2rdczh47tjes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
