You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I was recently looking into some messages logged by this library and I noticed that they were in a completely different format than our other log messages. After looking at the source code I realized that this library uses Apache Commons Logging instead of SLF4J as a logging facade. This is the first time I've even heard of Apache Commons Logging.
I was wondering if there was a strong conscious decision to use Apache Commons Logging instead of SLF4J. Apache Commons Logging appears to be a dead project with the last release in 2014 while SLF4J has had at least one release every year.
Apache Commons Logging does not work with the logging implementation we use (logback) but appears to work with a JCL to SLF4J bridge. If you are open to using SLF4J I would be happy to open a pull request.
The text was updated successfully, but these errors were encountered:
Hello. I was recently looking into some messages logged by this library and I noticed that they were in a completely different format than our other log messages. After looking at the source code I realized that this library uses Apache Commons Logging instead of SLF4J as a logging facade. This is the first time I've even heard of Apache Commons Logging.
I was wondering if there was a strong conscious decision to use Apache Commons Logging instead of SLF4J. Apache Commons Logging appears to be a dead project with the last release in 2014 while SLF4J has had at least one release every year.
Apache Commons Logging does not work with the logging implementation we use (logback) but appears to work with a JCL to SLF4J bridge. If you are open to using SLF4J I would be happy to open a pull request.
The text was updated successfully, but these errors were encountered: