You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2014/11/06 20:22:38 UTC
[jira] [Updated] (LOG4J2-892) JUL adapter does not map Log4j's
FATAL level to JUL level
[ https://issues.apache.org/jira/browse/LOG4J2-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory updated LOG4J2-892:
--------------------------------
Summary: JUL adapter does not map Log4j's FATAL level to JUL level (was: JUL adapter does not map Log4j'2 FATAL level to JUL level)
> JUL adapter does not map Log4j's FATAL level to JUL level
> ---------------------------------------------------------
>
> Key: LOG4J2-892
> URL: https://issues.apache.org/jira/browse/LOG4J2-892
> Project: Log4j 2
> Issue Type: Bug
> Components: JUL adapter
> Affects Versions: 2.1
> Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Gary Gregory
>
> JUL module does not map Log4j'2 FATAL level.
> See {{org.apache.logging.log4j.jul.DefaultLevelConverter}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org