Remko Popma created LOG4J2-517:
----------------------------------
Summary: Switch in log4j-1.2-api Category.getEffectiveLevel misses
FATAL, OFF
Key: LOG4J2-517
URL: https://issues.apache.org/jira/browse/LOG4J2-517
Project: Log4j 2
Issue Type: Bug
Components: log4j 1.2 emulation
Affects Versions: 2.0-beta9
Reporter: Remko Popma
Fix For: 2.0-rc1
Current:
{code}
public final Level getEffectiveLevel() {
switch (logger.getLevel().getStandardLevel()) {
case TRACE:
return Level.TRACE;
case DEBUG:
return Level.DEBUG;
case INFO:
return Level.INFO;
case WARN:
return Level.WARN;
default:
return Level.ERROR;
}
}
{code}
Should be:
{code}
public final Level getEffectiveLevel() {
switch (logger.getLevel().getStandardLevel()) {
case TRACE:
return Level.TRACE;
case DEBUG:
return Level.DEBUG;
case INFO:
return Level.INFO;
case WARN:
return Level.WARN;
case ERROR:
return Level.ERROR;
case FATAL:
return Level.FATAL;
default:
return Level.OFF;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
