[
https://issues.apache.org/jira/browse/LOG4J2-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647284#comment-15647284
]
Bernhard Mähr commented on LOG4J2-1443:
---------------------------------------
Fixed with 2.7.
Please close.
> Fallback to "default configuration" not working anymore
> -------------------------------------------------------
>
> Key: LOG4J2-1443
> URL: https://issues.apache.org/jira/browse/LOG4J2-1443
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.6, 2.6.1
> Reporter: Bernhard Mähr
>
> Until Version 2.5 I got the message
> {code}
> ERROR StatusLogger File not found in file system or classpath:
> ./log4j-test.xml
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console.
> {code}
> if the log4j-configuration file was missing. Starting with 2.6 it causes a
> {code}
> Caused by: java.lang.NullPointerException: No Configuration was provided
> {code}
> This is especially annoying for unit-tests because there is not always a
> log4j configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
