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 "Curt Arnold (JIRA)" <ji...@apache.org> on 2008/08/12 18:08:44 UTC
[jira] Created: (LOG4J2-23) log4j 2.0 should work without an
explicit configuration file
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
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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] Commented: (LOG4J2-23) log4j 2.0 should work without an
explicit configuration file
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867810#action_12867810 ]
Ralph Goers commented on LOG4J2-23:
-----------------------------------
My experimental branch provides a default configuration. In addition, any number of custom configuration implementations can be added via a plugin mechanism.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org