this worked well, resolved in https://issues.apache.org/jira/browse/SLING-4033
stefan
-Original Message-
From: Julian Sedding [mailto:jsedd...@gmail.com]
Sent: Friday, October 10, 2014 4:28 PM
To: dev@sling.apache.org
Subject: Re: Question on dependency management while adding a test
Hi Amit,
On Fri, Oct 10, 2014 at 10:57 AM, Amit.. Gupta. amitg...@adobe.com wrote:
Hello Team,
I am adding a test case of [0], for this I need to use latest of
groupIdorg.apache.sling/groupId
artifactIdorg.apache.sling.testing.resourceresolver-mock/artifactId
?
Hi Robert,
Currently tests are part of sling event module.
Thanks
-Amit
From: Robert Munteanu romb...@apache.org
Sent: Friday, October 10, 2014 1:41 PM
To: dev@sling.apache.org
Subject: Re: Question on dependency management while adding a test case
Hi
Hi Amit
We could change the resourceresolver-mock to use a lower Sling API
version than it implements. I.e. in MockResourceResolver, change all
resource.getValueMap() to ResourceUtil.getValueMap(resource). Then it
should be compatible with lower API versions. This should work as long
as there are
Rethinking this, can't we simply exclude the api dependency when
including the resourceresolver-mock ?
groupIdorg.apache.sling/groupId
artifactIdorg.apache.sling.testing.resourceresolver-mock/artifactId
exclusions
exclusion
groupIdorg.apache.sling/groupId
...@apache.org
Sent: Friday, October 10, 2014 8:17 PM
To: dev@sling.apache.org
Subject: Re: Question on dependency management while adding a test case
Rethinking this, can't we simply exclude the api dependency when
including the resourceresolver-mock ?
groupIdorg.apache.sling/groupId