You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/01/18 04:42:30 UTC

DO NOT REPLY [Bug 16039] - Log4J shutdown not invoked?

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16039

Log4J shutdown not invoked?

craig.mcclanahan@sun.com changed:

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



------- Additional Comments From craig.mcclanahan@sun.com  2003-01-18 03:42 -------
I don't believe that it is the responsibility of commons-logging to clean up
Log4J (or any other logging system), just as it is not the responsibility of
commons-logging to configure it in the first place.  This API is simply a
wrapper around the *logging* calls.  Configuration and lifecycle management of
the underlying logging implementation is the responsibility of the application
that is using commons-logging.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>