[
https://issues.apache.org/jira/browse/SLING-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated SLING-549:
--------------------------------
Attachment: SLING-549.patch
This patch implements a Scala scripting engine:
- Scala compiler 2.7.2 (most recent stable version)
- Scripts are compiled into /var/classes by default (configurable)
- Recompilation of scripts as needed
- Supports dynamic package import
- Pre-build binaries are available from the interim project page at
http://code.google.com/p/sling-scala/ (revision 129)
Possible improvements/changes
- Add configuration settings for compiler options
- Make the script wrapper more flexible
- Instead of rolling an own script wrapper, make Scripts implement the Servlet
interface
> Scala interpreter should use the current ClassLoader instead of rebuilding
> its own classpath
> --------------------------------------------------------------------------------------------
>
> Key: SLING-549
> URL: https://issues.apache.org/jira/browse/SLING-549
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-549.patch
>
>
> As the code at [1] demonstrates, the scala interpreter rebuilds its own
> classpath from the current JVM classpath and user-supplied additions.
> We should find a way for it to use the current classloader instead.
> Note that the almost same test [2] works when run with "mvn test" without
> setting the classpath explicitly, probably because in this case the JVM
> classpath includes the scala jars.
> [1]
> http://code.google.com/p/sling-scala/source/browse/trunk/scala-min-bundle/src/main/java/org/apache/sling/scripting/scala/minbundle/ScalaCompileServlet.java
> [2]
> http://code.google.com/p/sling-scala/source/browse/trunk/scala-min-bundle/src/test/java/org/apache/sling/scripting/scala/minbundle/ScalaCompilerTest.java?r=38
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
