- Split up
active-logger into
active-logger-api that uses the SLF4J facade as the "backend"- and
active-logger-timbre that uses timbre-slf4j as the backend and wraps timbre-specific stuff like configuration as active-logger does now
- Tie both together in
active-logger in such a way that it transparently provides the same functionality as it does now
active-logger is then useful for stand-alone applications as it is now, active-logger-api is then useful for libraries.
active-loggerintoactive-logger-apithat uses the SLF4J facade as the "backend"active-logger-timbrethat usestimbre-slf4jas the backend and wraps timbre-specific stuff like configuration asactive-loggerdoes nowactive-loggerin such a way that it transparently provides the same functionality as it does nowactive-loggeris then useful for stand-alone applications as it is now,active-logger-apiis then useful for libraries.