> > There are multiple logging APIs out there: Commons Logging, native > Log4j2 logging facade, slf4j, Java util logging. There used to be a > great deal of hatred directed at Commons Logging some while ago. We > cannot make everyone happy. It is easier to not impose a particular > choice of logging APIs unless necessary.
But like I said, the choice of logging API doesn't really matter all that much, because every logging API works with every logging framework. In my experience, only java.util.logging is a bit of a headache, because in addition to a logging bridge dependency it is necessary to set a system property. But I think most engineers would agree that this still beats having no logging at all! Besides, you seem to have made this choice on the client side anyway. And indeed, Slf4j works fine unless you really need to log FATALs for some reason. As naive as this sounds, I'll be surprised if someone complains about us adding Slf4j-api to core.
