[
https://issues.redhat.com/browse/ISPN-8283?page=com.atlassian.jira.plugin...
]
Dan Berindei resolved ISPN-8283.
--------------------------------
Fix Version/s: 10.1.1.Final
Resolution: Done
Fixed indirectly, in master
{{mvn dependency:tree | egrep "log4j|---------------"}} shows all the log4j
dependencies are in the {{test}} or {{provided}} scope.
Required runtime dependency to log4j
------------------------------------
Key: ISPN-8283
URL:
https://issues.redhat.com/browse/ISPN-8283
Project: Infinispan
Issue Type: Bug
Components: Build
Affects Versions: 8.2.7.Final
Reporter: Daniel H. Peger
Priority: Major
Fix For: 10.1.1.Final
Current versions of the 8.2.X release of infinispan declare a runtime dependency to
several log4j libraries. I noticed this for the artifacts
{{org.infinispan:infinispan-spring4-embedded}} and
{{org.infinispan:infinispan-spring4-common}} but there may be possibly others. These
dependencies may break the logging configuration of applications using infinispan as
log4j2 and the respective SLF4J binding is suddenly on the application classpath which may
happen unnoticed.
This dependency is not present in the most recent 9.1.0 artifacts anymore.
See the [SLF4J
documentation|https://www.slf4j.org/codes.html#multiple_bindings] for best
practices on using SLF4J.
This issue relates to ISPN-786 but is still present in infinispan 8.2.7
--
This message was sent by Atlassian Jira
(v7.13.8#713008)