[
https://issues.apache.org/jira/browse/SLING-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669723#action_12669723
]
Michael Dürig commented on SLING-549:
-------------------------------------
ok everything seems to work fine. The only thing I noticed is that the Scala
scripting engine is not buildable from sling\scripting\scala. If I try to do so
Maven fails with
[INFO] Project 'org.apache.sling:org.apache.sling.scripting.scala' is
duplicated in the reactor
If this is not easy to fix, I suggest to remove the reactor pom from that
location.
I'll follow up on the integration test later this week.
> Scala script engine
> -------------------
>
> Key: SLING-549
> URL: https://issues.apache.org/jira/browse/SLING-549
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
> Attachments: SLING-549-2.patch, SLING-549-3.patch, 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.
