[ 
https://issues.apache.org/jira/browse/SLING-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-8576.
-----------------------------------
    Fix Version/s: Testing Sling Mock 2.3.18
         Assignee: Stefan Seifert
       Resolution: Fixed

thanks, it's merged!
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/abaf290389f1a2066b98acc8a24419fd2bfdb55e


> NoClassDefFoundError for ScriptEngineManagerFactory
> ---------------------------------------------------
>
>                 Key: SLING-8576
>                 URL: https://issues.apache.org/jira/browse/SLING-8576
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing Sling Mock 2.3.14
>            Reporter: Hans-Peter Stoerr
>            Assignee: Stefan Seifert
>            Priority: Minor
>             Fix For: Testing Sling Mock 2.3.18
>
>
> When been upgrading our dependencies to the versions used in Sling Starter 
> 11, namely upgrading org.apache.sling.scripting.core to version 2.0.54, our 
> tests stopped working even when using the latest version 
> org.apache.sling.testing.sling-mock.core:2.3.14 with the following exception:
> java.lang.NoClassDefFoundError: 
> org/apache/sling/scripting/core/impl/ScriptEngineManagerFactory
> at 
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.registerDefaultServices(SlingContextImpl.java:153)
> at 
> org.apache.sling.testing.mock.sling.context.SlingContextImpl.setUp(SlingContextImpl.java:129)
> ...
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.sling.scripting.core.impl.ScriptEngineManagerFactory
> The problem here is that the class 
> org.apache.sling.scripting.core.impl.ScriptEngineManagerFactory exists in the 
> sling.scripting.core:2.0.36 , which is used as a dependency of 
> sling-mock.core, but does not exist anymore in sling-scripting.core:2.0.54. 
> It would be nice if that could be fixed!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to