The deal is that I am NOT the only one that wants this. It is rather silly to fork the code for this little thing, isn't it?? It's half an hours work with three classes, apparently. But I think that this one little method makes the whole system (quite) a bit less worth - and that's sad, because the rest of the system is totally excellent.
Maybe you can organize a "Log4j Trace Level Lobby Group" or, LTLLG for short. You can discuss your ideas about what exactly a Trace level is supposed to accomplish that can't be accomplished with other levels and agree on where exactly it fits into the hierarchy. Is more verbose than Debug? Is it between Debug and Info? Should it go somewhere else? These questions have not been pinned down and have only proliferated through various users' mismatched conceptions of what they think a TRACE level means to them. If it is added, would it also follow that other levels might be added such as FINE if people started requesting that? Where would those go? How many levels is enough for Log4j? When Domains are made available in a Log4j release, will they supercede Levels or enhance their functionality?
Anyway, those are just some thoughts. You don't need to reply to those questions on the list. Leave it for the LTLLG and come back with a definitive proposal.
Jake
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
