You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Grant Ingersoll <GS...@syr.edu> on 2004/12/09 19:13:48 UTC
JAR distribution
Hi,
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?
Thanks for the help,
Grant Ingersoll
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: JAR distribution
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
Another +1 to what Jake said, this time from the application server developer's
point of view (wearing my Tomcat hat at the moment).
Yoav
--- Ceki G�lc� <ce...@qos.ch> wrote:
> At 07:20 PM 12/9/2004, Jacob Kjome wrote:
> >Quoting Grant Ingersoll <GS...@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.
>
> +1
>
> >Jake
>
> --
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: JAR distribution
Posted by Ceki Gülcü <ce...@qos.ch>.
At 07:20 PM 12/9/2004, Jacob Kjome wrote:
>Quoting Grant Ingersoll <GS...@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.
+1
>Jake
--
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
Re: JAR distribution
Posted by Jacob Kjome <ho...@visi.com>.
Quoting Grant Ingersoll <GS...@syr.edu>:
> Hi,
>
> 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.
Jake
> Thanks for the help,
> Grant Ingersoll
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org