[
https://issues.apache.org/jira/browse/LOG4J2-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-707.
---------------------------------
Resolution: Fixed
Committed revision 1609251.
> Some exceptions are not logged when configuration problems are detected
> -----------------------------------------------------------------------
>
> Key: LOG4J2-707
> URL: https://issues.apache.org/jira/browse/LOG4J2-707
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-rc2
> Environment: Apache Maven 3.2.2
> (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
> Maven home: C:\Java\apache-maven-3.2.2
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\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
> Fix For: 2.0
>
>
> Some configuration code does not log exceptions. This is counterproductive
> for debugging.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
