Hi, lgoback seems to solve some problems that log4j has, but I did not yet find the answer to my most pressign question: Does logback handle multiple configurations in a controllable manner? The crucial problem with log4j was its great propularity not only with application developers but also with library developers that sometimes packed an log4j confguration file into their jars. So in almost every project it could happen that one did configure log4j and only get strange or even no output because ther is some other log4j configration overriding the one intended by oneself. If logback improves this behavior of log4j I'd be switching immediately with flying colors! Regards, jens
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
_______________________________________________ Logback-user mailing list [email protected] http://qos.ch/mailman/listinfo/logback-user
