logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: JAR distribution
Date Thu, 09 Dec 2004 18:25:10 GMT
At 07:20 PM 12/9/2004, Jacob Kjome wrote:
>Quoting Grant Ingersoll <GSIngers@syr.edu>:
> > Was wondering if someone could offer insight on how they control
> > logging in libraries they are delivering to other companies?  I would
> > like to make the logging in the JARs we deliver fixed for a given
> > client.  That is, I don't want them to be able to override my logging
> > level declarations with their own log4j.properties.  Is there a way to
> > do this?  Do I just make sure my log4j.properties is in the Classpath
> > specified in a Manifest file?
> >
>Please, please, don't do this.  This will mess up logging configuration 
>for the
>application developer.  Logging is not for your purposes, it is for the end
>user's purposes.  A developer can turn off logging by default by setting the
>root logger to a very high level and then specify other specific loggers 
>to log
>at a lower level.  Don't include a config file in the jar.  Just provide
>instructions as to how to configure logging.



Ceki Gülcü

  The complete log4j manual:  http://qos.ch/log4j/  

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

View raw message