3 ms·
Just about every project used Log4j. When they added logging to the JDK they shipped logging support which was worse than what everyone was already using (log4j
by thescrewdriver 12y ago
Just about every project used Log4j. When they added logging to the JDK they shipped logging support which was worse than what everyone was already using (log4j), so adoption was very limited.
- jburwell 12y agoWhich in turn gave rise to the horrors of commons-logging (clogging) attempting to wrap both APIs and magically detect your logging framework with nasty classloader tricks. While slf4j is a very sane and useful wrapper, it shouldn't be necessary -- JDK logging should have been the wrapper API providing an SPI to plugin implementations (e.g. log4j, logback, etc).
- MrBuddyCasino 12y agoRight - fixing it in that case means "do the same as thing as with Joda, but do it with slf4j and logging instead".
- jburwell 12y agoAt this point, it is attempting the close the barn door after the horses have run half way around the world. Too much many systems have been built up on clogging and SLF4J. "Fixing" it now just add a third wrapper to the mix would not be a Good Thing(tm), IMHO. Sadly, it's as fixed as it is ever going to get at this point.