DO NOT REPLY [Bug 32885] - Log4j should have a default Console configuration when it doesn't find the properties file

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32885>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32885


ceki@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From ceki@apache.org  2005-01-03 14:44 -------

As of version 1.3, log4j is self-reliant for its own logging. In
particular, within the configuration phase, log4j may generate log
messages. These are replayed after log4j is fully configured. The fact
that log4j does not rely on a default configuration makes such
reentrant behavior tractable. Note that as of version 1.3, log4j no
longer emits the dreaded messages.

 log4j:WARN No appenders could be found for logger (foo).
 log4j:WARN Please initialize the log4j system properly.

Moreover, components using ULoggers (UGLI interface) may swap
ugli-simple.jar instead of log4j.jar. This will engage a default
behavior very similar to what you describe. 

For more details on UGLI please see

  http://logging.apache.org/log4j/ugli.html



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org