Hi, any idea why <ktor-client-tests-jvm> depends on `logback-classic` as an implementation dependenc...

# ktor

[suresh]

Hi, any idea why ktor-client-tests-jvm depends on logback-classic as an implementation dependency instead of slf4j? This causes issue when we need slf4j-simple for common jvm tests but throws the following warning.

CommonTest[jvm] > httpClient()[jvm] STANDARD_ERROR
    SLF4J(W): Class path contains multiple SLF4J providers.
    SLF4J(W): Found provider [org.slf4j.simple.SimpleServiceProvider@7adfe306]
    SLF4J(W): Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@7b0453f4]
    SLF4J(W): See <https://www.slf4j.org/codes.html#multiple_bindings> for an explanation.
    SLF4J(I): Connected with provider of type [org.slf4j.simple.SimpleServiceProvider]

[Aleksei Tirman [JB]]

Can you tell me why you need to use this artifact?

[ephemient]

as I mentioned in the other thread, it seems to be setup for tests inside the ktor repo

[ephemient]

in that usage, it makes sense to pull in logback-classic - it's a leaf node, not a library