Log4j 1.2.15: What’s With All These Dependencies?
September 19, 2007 – 16:55 | javaI may not necessarily agree with Weiqi Gao’s opinion that Log4j Must Die, but I have to admit that I really think the new mandatory dependencies added by log4j 1.2.15 are going over the board. To add insult to injury, some of those dependencies - namely com.sun.jdmk.jmxtools and com.sun.jmx.jmxri - aren’t actually available in any public repository due to license reasons.
Ironically I just commented on Weiqi’s aforementioned post that the major driving force for us to stay with log4j is its flexible configuration and powerful ability to interact with various message sinks. I mean those are all great things to have, but in the meanwhile could the good folks at log4j please change those dependencies to ‘optional’ or even ‘provided’, unless it’s really, really dependded on by the core log4j?
del.icio.us
digg this
reddit
dzone
Stumble it
4 Responses to “Log4j 1.2.15: What’s With All These Dependencies?”
I agree, it’s the primary reason I didn’t upgrade. Then again, it’s only an issue for Maven users AFAIK.
By Matt Raible on Sep 19, 2007
Ivy users too, most of whom also rely on the maven repositories.
By Jing Xue on Sep 19, 2007
This is being fixed - they’re optional (not required by core log4j).
By Scott Deboy on Sep 19, 2007
death to log4j.. JDK logger is good enough..
By afsina on Sep 20, 2007