Every few months this come up. Every time it has to be "put to rest". I've also used log4j since right before it moved to jakarta. I've seen this issue so many times. The examples of how to make "new levels", what do they use? Trace. It is ridiculous fighting it. And it somewhat pisses me off that THERE ACTUALLY IS (at least seems like) a rather overwhelming desire FOR it, as opposed to AGAINST it, which is totally neglected.
"Challenge": If Ceki is so sure about his haevy-handed decision, why DON'T he put the question up for a vote? A user-base vote?
Given that we are all striving to make log4j a better tool, I would like to avoid:
1) a war of trenches about this topic 2) make a personal issue out of this topic 3) having people perceive screaming as an efficient pattern of discussion in order to get things moving.
Ceki, you're a great guy, judging from your efforts with log4j and Apache in general, but this fighting against -your own user base- is annoying.
Please see point 2 above.
.. and what is NOT putting up the trace issue for vote gonna do?
See point 1 above.
Endre.
PS: If it is interesting, I could make some suggestions, in the javadoc, for when to use the different levels - I feel that it lacks such guidance for firsttime users. As we at our organization have used it for such a long time, I think I've gotten a pretty clear idea of which things should go where - and I actually firmly believe that this would be pretty objective.
Good suggestion. Would you care to add an explanation on levels on the log4j wiki?
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp import org.apache.Facetime;
ApacheCon US 2003, 18-21 November http://apachecon.com/--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
