Its always painful to explicitly exclude a logging-framework dependency from a library, so please only depend on slf4j-api. The selection of the logging framework should be made by the user of the library (ie. the application). If you need the slf4j-log4j binding for logging during unit-tests, bind it to test scope.
Taken from www.slf4j.org/manual.html:
"Please note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api."
Its always painful to explicitly exclude a logging-framework dependency from a library, so please only depend on slf4j-api. The selection of the logging framework should be made by the user of the library (ie. the application). If you need the slf4j-log4j binding for logging during unit-tests, bind it to test scope.
Taken from www.slf4j.org/manual.html: "Please note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api."
kind regards