*** The wcm.io Project is closing down this JIRA Instance in favor of GitHub issues. *** Please use the corresponding GitHub projects to report issues - or the mailing list for general discussion.

Issues

Select view

Select search mode

 

Exclude "sl4fj-simple" from transitive dependencies of aem-mock.core

Won't Fix

Description

When a project has both aem-mock.core as well as uber-jar as dependency you always get the following WARN:

slf4j-simple is a transitive dependency of sling.models.impl and should be explicitly excluded in aem-mock.core.

Attachments

1

Details

Assignee

Reporter

Components

Affects versions

Priority

Created November 24, 2021 at 9:36 AM
Updated November 30, 2021 at 8:52 AM
Resolved November 30, 2021 at 8:52 AM

Activity

Show:

Stefan SeifertNovember 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 WindszusNovember 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 SeifertNovember 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 SeifertNovember 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 WindszusNovember 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)

Loading...