https://bz.apache.org/bugzilla/show_bug.cgi?id=63046
--- Comment #3 from Axel Howind <a...@dua3.com> --- I think technical there's not much difference between SLF4J and Log4j2 regarding lock-in. Both separate API and Implementation (which was not the case with the old log4j) and can be used with different backends. You can use log4j2 and log to any SLF4J backend or vice-versa. But honestly, there doesn't seem to be much life left in SLF4J. The last check-in is from march 2018. Just have a look at the repo and the dev list. Same goes for logback (same dev). SLF4J now already lacks features that the JDK Logger introduced in JDK 8 (message suppliers to prevent creating temporary objects being an example). The SLF4J feature request dates from 2016, and it doesn't seem there will be much happening anytime soon. Maybe it would be worth reaching out to Ceki/qos and ask if SLF4J is still alive before deciding. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
