[ https://issues.apache.org/jira/browse/SLING-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703172#action_12703172 ]
Bertrand Delacretaz commented on SLING-928: ------------------------------------------- Tests run fine against an already started Sling instance, but not when Sling is started by the cargo maven plugin when running "mvn clean install" in contrib/launchpad/testing. Steps to reproduce: 1. In contrib/launchpad/testing run mvn clean integration-test -Dintegration.test.wait=true this starts Sling with the same environment used for integration testing. 2. Try to look at the OSGi console's script engines page at http://localhost:8888/org.apache.sling.launchpad.contrib-testing-4-incubator-SNAPSHOT/system/console/scriptengines This causes the following exception: java.lang.NullPointerException at org.apache.sling.scripting.scala.interpreter.BundleFS$BundleEntry$1.getPathAndName(BundleFS.scala:71) at org.apache.sling.scripting.scala.interpreter.BundleFS$BundleEntry$1.x$1(BundleFS.scala:39) at org.apache.sling.scripting.scala.interpreter.BundleFS$BundleEntry$1.name(BundleFS.scala:39) at scala.tools.nsc.symtab.SymbolLoaders$PackageLoader$$anonfun$refresh$1$$anonfun$apply$1.apply(SymbolLoaders.scala:173) Probably related to the fix of revision 769024, but I'm not sure how to fix that in the scala code. > Include integration tests for Scala scripting engine > ---------------------------------------------------- > > Key: SLING-928 > URL: https://issues.apache.org/jira/browse/SLING-928 > Project: Sling > Issue Type: Improvement > Components: Testing > Reporter: Michael Dürig > Assignee: Bertrand Delacretaz > Attachments: SLING-928-pom.patch, SLING-928.patch > > > Include integration tests for the Scala scripting engine in > contrib\launchpad\testing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.