How does slf4j bind to implementation? Does it really do so during compile time?

Question

In the documentation for slf4j it says that the binding happens during complie time:

\"SLF4J does not rely on any special class loader machinery. In fact, each SLF4J bi

Answer 1

The implementation is not bound at compile-time (it's not a static/early binding) or in other words the implementation it's not known at compile time.

Actually it's the vice-versa where the implementation is bound at runtime, meaning that the implementation is discovered through dynamic/runtime binding . The Slf4j folks have actually declared how the binding happens in their manual https://www.slf4j.org/manual.html:

SLF4J allows the end-user to plug in the desired logging framework at deployment time.