Howdy, >It does not really matter what TRACE level gets used for. Each development >team / organization will have their interpretation of it depending on how >they intend to use the information logged at both levels.
I agree, it doesn't matter what it's used for, only if it's used at all. >More importantly - having a level more verbose than DEBUG is very handy. We Very handy for you. >1. TRACE level >2. An extension of DailyRollingFileAppender that also uses filesize as a >rolling criterion >3. MBeans support Would you consider 2 and 3 as important to the core of log4j as 1 above? Clearly you think 1 belongs in the native log4j core. The point I'm making is not as much about the TRACE level per se. I know some people want it and use it. It's about adding a feature to the core of a product where: - It's not clear how useful the feature is, and - It's not clear what the backwards compatibility implications are, especially for organizations that already have their own custom TRACE level (or other levels that go between DEBUG and OFF). Hypothetically speaking, let's say there was a log4j sandbox jar with a Level class replacement that includes a TRACE (and maybe FINE, FINER, FINEST, REALLY_FINEST, ABSOLUTELY_FINEST, IT_CANT_GET_ANY_FINER, etc ;) -- just kidding) level, would that be useful for people? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
