I don't think the two have to be mutually exclusive - we can enhance 'custom level' support via a new mechanism and add built-in support for the new levels as well.
I personally don't think they're confusing, as folks have mentioned, httpd uses them. I used to think of levels as 'severities', but that's really only true for a subset of levels we have now (trace isn't really a severity, right? and fatal, well, it's never used), so my gut says these new levels support the 80/20 rule for 'custom levels' Chainsaw/ExpressionFilter etc (assuming log4j2 support) will have to deal with this eventually (level > DEBUG) etc, but I don't think that's a big deal. Scott On 1/23/14, Ralph Goers <ralph.go...@dslextreme.com> wrote: > Remko, are you saying that if we make the changes proposed in the other > thread that we should not add any of these levels to the new Level class? > > Ralph > > On Jan 23, 2014, at 1:22 AM, Remko Popma <remko.po...@gmail.com> wrote: > >> Gary, >> >> Would you mind rolling back the changes you made in revision 1560602 (and >> perhaps r1560356)? >> This change added DIAG, VERBOSE, NOTICE log levels to many files. >> I don't think we all agreed on that approach and we have some promising >> ideas for an alternative solution that should satisfy everyone. >> >> Best regards, >> Remko > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
