https://issues.apache.org/bugzilla/show_bug.cgi?id=25747
Curt Arnold <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #2 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-12 10:03:44 PST ---
Disabling logging when no configuration could be found was a explicit design
issue since certain environments (such as Webapps) logging to the console is
undesirable.
JDK 1.4 logging has a fallback configuration file that is provided with the
JDK, so it never runs into the lack of configuration problem. log4j 2.0 could
possibly delegate to JDK 1.4 logging if no other configuration was found.
Added issue LOG4J2-23 for that.
Added a message pointing to the FAQ, but there is not much that we can easily
do to display the class loader's strategy for locating resources.
Committed rev 685228.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
