> Generally that's true but for logging there's not a lot to it. Think of > SLF4J as an API, much like the servlet API. I don't think of my self as > being tied to SLF4J as me coding against a simple logging API.
Even when I code to the servlet API, I do not make it a *mandatory* dependency in a product or framework. It is part of the whatever-web.jar. If you want web support, add whatever-web.jar to your classpath (or include it in an uber jar). I still code with the concept that the core part of the framework is not dependent on any API except the base JRE. That cannot be the case when using SLF4J embedded directly into every class file where we need logging.
