Hm, I feel that something is wrong with logging and especially kotlin-logging:
[kotlin-logging is a] logging library wrapping slf4j with Kotlin extensions.
So, you would have
- a wrapper (kotlin-logging) for
- a facade (slf4j) which, in the case of Log4j 2, would use
- Log4j API which in turn would use
- Log4j implementation.
And all that without any real benefit over using Log4j API directly. For the case that you are not familiar with Log4j 2 API – it is the equivalent to slf4j, but more modern (uses lambdas for example). Other frameworks could adapt this API as well. See Go ahead: program to the log4j2 API instead of slf4j