gt;To: users@sling.apache.org
>Subject: Re: sling mocks "Creating resource resolver failed"
>
>Hi again,
>
>Coming back a bit on this.
>
>It seems the the point is that the version of the sling api and the
>resourceResolver you use need to match, and this needs to be done
Hi again,
Coming back a bit on this.
It seems the the point is that the version of the sling api and the
resourceResolver you use need to match, and this needs to be done explicitly in
your pom.
This is more clear in the sling-mock source code. It has a profiles that uses
different versions
>I tried updating the resourceresolver version to 1.5.22 but got a different
>error:
just hit this as well - also try osgi-mock 2.2.5-SNAPSHOT with the fix from
SLING-6811
stefan
org.apache.sling.resourceresolver 1.4.8
org.apache.sling.api 2.16.2
I tried updating the resourceresolver version to 1.5.22 but got a different
error:
java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
factory: Unable to invoke method 'activate' for class
org
>Subject: Re: sling mocks "Creating resource resolver failed"
>
>Hi Stefan,
>
>Sure. I think most of it is in the newest or a very recent version.
>
>Sling-mock 2.2.6
>ResourceResolver-mock 1.1.16
>sling-mock-oak 2.0.2
>jcr-mock 1.2.0
>org.apache.sling.j
can you provide more details with version of sling mock you are using?
and if you are overrding some of it's dependencies (e.g.
org.apache.sling.resourceresolver or org.apache.sling.jcr.resource) with other
versions?
you might also try to move sling-mock test dependency to the top in your
