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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/05/01 06:27:45 UTC
[jira] [Resolved] (LOG4J2-23) log4j 2.0 should work without an
explicit configuration file
[ https://issues.apache.org/jira/browse/LOG4J2-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-23.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
Log4j 2 uses a default configuration.
> log4j 2.0 should work without an explicit configuration file
> ------------------------------------------------------------
>
> Key: LOG4J2-23
> URL: https://issues.apache.org/jira/browse/LOG4J2-23
> Project: Log4j 2
> Issue Type: Wish
> Components: log4j 1.2 emulation
> Reporter: Curt Arnold
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> log4j 1.2 will display a warning and ignores log requests if no configuration file is found and no explicit configuration is performed. JDK 1.4 logging has a last-chance configuration file installed in the JDK. log4j 2.0 should consider delegating to JDK 1.4 logging when no configuration is available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org