On 2013-03-27 16:36, Gary Gregory wrote:
I think we can discuss both issues separately: (1) more level and (2)
how they show up in the API.
(1) Let's discuss the merits how more log levels. Should we go the
Apache HTTPD route? version 2.2? 2.4?
My 2c is that the people requiring more levels and configurable levels
are sufficiently small in number that they should roll their own solution.
It's rough, but at some point we have to balance things like
maintainability and ease of use vs. solving every single niche situation.
Adding configurable levels requires that a lot of different parts of the
log4j code, as well as plugin authors, will have to pay a "development
tax" for a feature that will only be used by a minuscule minority of
log4j users.
Regards, Noel Grandin
Disclaimer: http://www.peralex.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
