See the section "Conditional configuration" in [1]. The hostname is automatically exported in a field called 'hostname'. This field is not visible in nested scopes. See the section "Automatically exported fields" in the docs. HTH, [1] http://logback.qos.ch/manual/groovy.html On 08/07/2010 1:47 PM, Grzegorz Borkowski wrote:
I see. Do you have any examples of such config? How can you decide in this conditional statements what kind of environment it executes in? Still, I think it should be better explained in docs. Now docs say "you can use logback.xml and logback-test.xml, and that's ok; you can also use groovy instaed of logback.xml" - so natural question is "and what with logback-text.xml then"? Anyway, if logback supports two xml files for config, it should support two groovy files too, I think. Just to make it clear and consitent. And to prevent questions like mine in the future :)
W dniu 2010-07-08 13:07, Ceki Gülcü pisze:
Hello Greg,
Assuming that the development host is different than the production host, you can use conditional statements in logback.groovy to cater for both environments. This is what we now do internally at QOS.ch and find it more convenient than having two distinct config files.
Holler if you need help with conditional statements in logback.groovy. Your feedback on your experiences with logback.groovy is also welcome.
Cheers,
On 08/07/2010 11:34 AM, Grzegorz Borkowski wrote:
Now when we can replace logback.xml with logback.groovy, what happened to logback-test.xml? I see no hint in documentation what to do with it. For sure there is no point in having one file written in groovy, and another one (for tests) in XML. So will logback-test.groovy work? Greg
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user