Exclude "sl4fj-simple" from transitive dependencies of aem-mock.core
Description
Attachments
- 29 Nov 2021, 06:42 PM
Activity
Stefan Seifert November 30, 2021 at 8:52 AM
for the AEM dependencies i decided to switch to 1.4.14 for the test classpath because for the unit tests it should not make any noticeable difference and will update to next version once its released and included in AEM.
Konrad Windszus November 30, 2021 at 8:45 AM
Right, I am using my own dependency management in this case which uses 1.4.16. But I agree, probably nothing to fix here but rather in my dependency management and also with a release of Sling Models Impl.
Stefan Seifert November 30, 2021 at 8:34 AM
which AEM dependencies version are you using (if at all)? all (latest) released version should have version 1.4.14 referenced because of this problem. and 1.4.14 does not have this dependency. please check from where this 1.4.16 dependencies is coming form, not from an wcm.io AEM dependencies POM.
Stefan Seifert November 30, 2021 at 8:33 AM
uh, we still did not release a new version of sling models.impl, it was fixed on master.
i will update the affected aem dependencies POMs with excludes for org.apache.sling.commons.testing
Konrad Windszus November 29, 2021 at 6:42 PM
In my case this is caused by a managed version of sling models impl (AEM 6.5.10 ships with 1.4.16)
When a project has both
aem-mock.core
as well asuber-jar
as dependency you always get the following WARN:SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/konradwindszus/.m2/repository/org/slf4j/slf4j-simple/1.7.25/slf4j-simple-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/konradwindszus/.m2/repository/com/adobe/aem/uber-jar/6.5.10/uber-jar-6.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
slf4j-simple is a transitive dependency of sling.models.impl and should be explicitly excluded in aem-mock.core.