Instead of directly depending on log4j, using the SLF4J logging facade will allow dependent applications of the Sparkpost library to pick/configure a logging library of their choice or at least not conflict with different versions of log4j.
The use case for me was that I'm using the logback logging library in my application, but the sparkpost library required me to configure both log4j and logback to have the same kind of logging formats, levels, and appenders.
I'll be submitting a PR in a few that contains the changes necessary for this.
Instead of directly depending on log4j, using the SLF4J logging facade will allow dependent applications of the Sparkpost library to pick/configure a logging library of their choice or at least not conflict with different versions of log4j.
The use case for me was that I'm using the logback logging library in my application, but the sparkpost library required me to configure both log4j and logback to have the same kind of logging formats, levels, and appenders.
I'll be submitting a PR in a few that contains the changes necessary for this.