2) make a personal issue out of this topic
Since all use of any level is subjective, a refusal to add a TRACE level, that seems to be a highly request feature, can only be seen as a "personal" issue already. It has already been established that domains will not replace levels, so for those that may not have the option of moving to the use of domains, a TRACE level is still an unmet need.
How was it established that domains will not replace levels?
Lets be realistic about this issue. A vote is not needed here, adding a trace level would not change any existing functionality. Those that do not want it do not have to use it. I can only see two valid reasons for not including TRACE as a natively supported level.
1) No resources available to implement, test or maintain the change. 2) Change is incompatible with or contrary to current functionality
There is also:
3) Change works contrary to future functionality.
I would think that any other reason for rejection would leaning toward the "personal". Since the addition of a TRACE level could hardly be seen as being incompatible, would a contribution of the patch to add the native support for the TRACE level be accepted from an "non-comitter"?
The implementation question is hardly an issue here.
Some users are asking for the TRACE level. My response was: please wait for the domain functionality to crystallize and then, if you remain unconvinced, let us have this discussion again.
I think it is very unfair to qualify our reaction on this matter as condescending or trivializing [the requested change]. If my memory serves me correctly, this is the first flame war on this mailing list, ever. I am actually not sure what to make of it.
-- 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]
