[
https://issues.apache.org/jira/browse/SLING-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346805#comment-14346805
]
Chetan Mehrotra commented on SLING-4470:
----------------------------------------
In Jackrabbit Oak we use Logback for testcase and have a custom
logback-test.xml. So having multiple provider would cause issue as only one
would be picked and in our case we want the Logback one to be used.
bq. if we remove this dependency or change it to "test" it is not active in the
project that has the test code and on every project you would have to include
slf4j-simple and a matching logging configuration yourself to ensure a proper
logging setup
I think that should be the way. OSGi Mock is a library which the project use
and it should not effect the way logging happens in the project. That should be
left to project to decide
> OSGi mock has compile time dependency on slf4j-simple
> -----------------------------------------------------
>
> Key: SLING-4470
> URL: https://issues.apache.org/jira/browse/SLING-4470
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.2.0
> Reporter: Chetan Mehrotra
> Priority: Minor
>
> org.apache.sling.testing.osgi-mock has a compile time dependency on
> slf4j-simple which triggers warning by slf4j
> {noformat}
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/home/user/.m2/repository/ch/qos/logback/logback-classic/1.1.0/logback-classic-1.1.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/home/user/.m2/repository/org/slf4j/slf4j-simple/1.7.6/slf4j-simple-1.7.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> {noformat}
> Scope for slf4j-simple should be test or provided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
