
I'm another happy, impressed LOGBack user who has very similar needs. Where I develop, we have several different deployment levels, all of which require substantially different logging configurations (e.g., development, qa, staging, production). However, our standard rollout procedure currently produces one standard build, as a zip file, for QA and above. We control the configuration in our startup with a few environment variables. As I start to push for my team's adoption of LOGBack, some mechanism like the one proposed below will be essential. I can't see any reason why I couldn't include a base logging configuration file in the classpath as a springboard to the configurable logging location. It would be convenient to specify the location for quick-and-dirty hacks, but I could live without it. The only drawback is that Log4j offers this, so there may be some in my group who protest changing to an implementation they may call “incomplete.” That said, if I could only have one, it would definitely be the inclusion mechanism. I’m not yet familiar with Joran, but it would be great if we could include some configure kind of mapping that along the lines of the below (pidgin pseudocode, but I think it's pretty clear). logName = case ENV{'env'} of 'qa' -> 'qa-logback.xml' 'dev' -> 'log-dev.xml' 'prod' -> 'logback.xml' logLocation = concat(ENV{'root'}, '/config/', logName) As long as I can control the location of the file with an environment variable, I can make things work, but it would be great to make the file location a function of one or more variables as above. Thank you, Andy Gerweck -----Original Message----- From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Ceki Gülcü Sent: Thursday, February 08, 2007 11:51 AM To: logback users list Subject: RE: [logback-user] add property for specifying logback.xmlfilelocation Hi Michael, What you propose makes sense. However, I'd like to limit the number of ways logback can be configured (to ease the brain-footprint of logback on our users.) How about if we allowed a config file to include parts from a different sources? This inclusion feature should allow you to reference a different file. Moreover, since Joran supports variable substitution, you could set the value of the variable through a system property. You would get the feature you are asking for, and we would keep the initialization procedure simple (err, simpler.). WDYT? If you agree, could you please file a bug report asking for inclusion feature in joran/logback? At 07:08 PM 2/8/2007, Newcomb, Michael-P57487 wrote:
If I have multiple tests that measure performance, debugging, vs. ??? I
don't want to change the file or have duplicate files in different directories.
Look at the logback examples directory.
logback-0.9\logback-examples\src\main\java\chapter2\
There are 3 different configuration files. I don't want any code
dependencies on Logback so the only way to configure logback is to use a
file called logback.xml or logback-test.xml.
To execute chapter 2 I would have to copy those files to logback.xml or
logback-test.xml. Or put them in different directories and rename them all
to the same file name.
Thanks,
Michael
-----Original Message-----
From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On
Behalf Of Sebastien Pennec
Sent: Thursday, February 08, 2007 12:36 PM
To: logback users list
Subject: Re: [logback-user] add property for specifying logback.xml
filelocation
Hello Michael,
At the moment, logback can load two different files: logback.xml and
logback-test.xml. They need to be in the classpath and can be useful to
separate the environments, e.g. development and production.
This behavior is usually enough for many situations.
Can you precise your request with a use case that would need a java
variable and would not be possible with the actual behavior?
Thanks,
Sébastien
Newcomb, Michael-P57487 wrote:
e.g.:
-Dch.qos.logback.config=foo/bar/my-logback.xml
Thanks,
Michael
----------------------------------------------------------------------
--
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
--
Sébastien Pennec
sebastien@qos.ch
Logback: The reliable, generic, fast and flexible logging framework for Java.
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ****************************************************************************