I recently learned that instead of using SFL4J’s API and the wanted implementation, you’d use System.Logger which is available since Java 9. Let’s see how.
Join the DZone community and get the full member experience. December was not a good time for Java developers and even less for Ops. The former had to repackage their apps with a fixed Log4J’s version, and the latter had to redeploy them — several times. Yet, every cloud has a silver lining. In my case, I learned about System. Logger. In short, System. Logger is a façade over your logging engine. Instead of using, say, SFL4J’s API and the wanted implementation, you’d use System. Logger instead of SLF4J. It’s available since Java 9, and it’s a bummer that I learned about it only recently. The API is a bit different than other logging APIs: it avoids different logging methods such as debug(), info() in favor of a single log() one where you pass a logging Level parameter.
