Thanks for the reasoning. I understand the issue. I guess then, the better question, is what are best practices for defining log messages under these circumstances. I want the debug and info messages available for me, but I don't want our clients to see these (they can see warn and above). I don't even want them to have the option of seeing these, which means the "tell them how to configure it" option isn't viable. The jar file in question is a Utilities jar file that is used by many of our projects, and is distributed with the project to clients. The clients use our project/application code which then uses the utilities code. Our current strategy is remove all of the logging, which I obviously don't like.
Any thoughts? I guess I may need to revisit why we have this requirement if nothing works. Thanks, Grant >>> [EMAIL PROTECTED] 12/9/2004 1:46:15 PM >>> 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� <[EMAIL PROTECTED]> wrote: > At 07:20 PM 12/9/2004, Jacob Kjome wrote: > >Quoting Grant Ingersoll <[EMAIL PROTECTED]>: > > > > > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
