February 2013 - logback-dev

Re : Re : stop() and start() on LoggerContext
by Mathieu Stempell 23 Feb '13

23 Feb '13

...and correcting myself a bit as i figured that only ContextInitializer autoConfig() was required after LoggerContext stop() & start(), as the stop() call already do reset(). It's a really nice library to work with by the way, finely extendable. Mathieu ----- Message d'origine ----- De : Mathieu Stempell Envoyés : 21.02.13 15:15 À : logback developers list Objet : [logback-dev] Re : stop() and start() on LoggerContext Replying to myself as i found the solution over the web. I had to call LoggerContext reset() and then ContextInitializer autoConfig() for the logging to be effective again after LoggerContext stop() & start(), as described here : http://stackoverflow.com/a/3810936 Mathieu ----- Message d'origine ----- De : Mathieu Stempell Envoyés : 20.02.13 15:28 À : logback-dev(a)qos.ch Objet : [logback-dev] stop() and start() on LoggerContext Hello, When i call start() method on LoggerContext after i called stop(), i doesn't log anything new in the output files : ----------- LoggerContext loggerContext = (LoggerContext)LoggerFactory.getILoggerFactory(); LoggerFactory.getLogger(AbstractTest.class).info("test info before stop"); // logs, ok loggerContext.stop(); LoggerFactory.getLogger(AbstractTest.class).info("test info between stop and start"); // doesn't log, ok loggerContext.start(); LoggerFactory.getLogger(AbstractTest.class).info("test info after start"); // doesn't log, why??? ----------- Is it normal or not? Thanks in advance for your anwser. Mathieu

1 0

[JIRA] (LOGBACK-805) DBAppender assumes that caller data is available on the event
by Darius X. (JIRA) 21 Feb '13

21 Feb '13

1 0

[qos-ch/logback-audit] 49292b: align css files with main logback site
by Ceki Gulcu 21 Feb '13

21 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-audit Commit: 49292b9b5729a9b7fa8a2493517bbfcdea6dd552 https://github.com/qos-ch/logback-audit/commit/49292b9b5729a9b7fa8a2493517b… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/css/common.css M audit-site/src/site/pages/css/prettify.css M audit-site/src/site/pages/css/screen.css M audit-site/src/site/pages/templates/left.js Log Message: ----------- align css files with main logback site

1 0

[qos-ch/logback-audit] 7d5d20: minor edits
by Ceki Gulcu 21 Feb '13

21 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-audit Commit: 7d5d206a106c51cbc1c04e311cf719072e616ae6 https://github.com/qos-ch/logback-audit/commit/7d5d206a106c51cbc1c04e311cf7… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/mailinglist.html M audit-site/src/site/pages/templates/left.js Log Message: ----------- minor edits

1 0

[qos-ch/logback-audit] 1e5bae: typo fix
by Ceki Gulcu 21 Feb '13

21 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-audit Commit: 1e5baea7a0e687b874ce45d6d11539055fc3f697 https://github.com/qos-ch/logback-audit/commit/1e5baea7a0e687b874ce45d6d115… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/faq.html Log Message: ----------- typo fix Commit: 19b14868bc7ba35fc271f0f64c4f029f57728192 https://github.com/qos-ch/logback-audit/commit/19b14868bc7ba35fc271f0f64c4f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/bugreport.html M audit-site/src/site/pages/faq.html M audit-site/src/site/pages/manual/Invoking_lba.html M audit-site/src/site/pages/manual/Running_the_Server.html M audit-site/src/site/pages/manual/index.html M audit-site/src/site/pages/manual/introduction.html Log Message: ----------- update css links Compare: https://github.com/qos-ch/logback-audit/compare/13f760ccc083...19b14868bc7b

1 0

Re : stop() and start() on LoggerContext
by Mathieu Stempell 21 Feb '13

21 Feb '13

Replying to myself as i found the solution over the web. I had to call LoggerContext reset() and then ContextInitializer autoConfig() for the logging to be effective again after LoggerContext stop() & start(), as described here : http://stackoverflow.com/a/3810936 Mathieu ----- Message d'origine ----- De : Mathieu Stempell Envoyés : 20.02.13 15:28 À : logback-dev(a)qos.ch Objet : [logback-dev] stop() and start() on LoggerContext Hello, When i call start() method on LoggerContext after i called stop(), i doesn't log anything new in the output files : ----------- LoggerContext loggerContext = (LoggerContext)LoggerFactory.getILoggerFactory(); LoggerFactory.getLogger(AbstractTest.class).info("test info before stop"); // logs, ok loggerContext.stop(); LoggerFactory.getLogger(AbstractTest.class).info("test info between stop and start"); // doesn't log, ok loggerContext.start(); LoggerFactory.getLogger(AbstractTest.class).info("test info after start"); // doesn't log, why??? ----------- Is it normal or not? Thanks in advance for your anwser. Mathieu

1 0

stop() and start() on LoggerContext
by Mathieu Stempell 20 Feb '13

20 Feb '13

Hello, When i call start() method on LoggerContext after i called stop(), i doesn't log anything new in the output files : ----------- LoggerContext loggerContext = (LoggerContext)LoggerFactory.getILoggerFactory(); LoggerFactory.getLogger(AbstractTest.class).info("test info before stop"); // logs, ok loggerContext.stop(); LoggerFactory.getLogger(AbstractTest.class).info("test info between stop and start"); // doesn't log, ok loggerContext.start(); LoggerFactory.getLogger(AbstractTest.class).info("test info after start"); // doesn't log, why??? ----------- Is it normal or not? Thanks in advance for your anwser. Mathieu

1 0

[JIRA] Created: (LBCORE-200) Add possibility to mark included file/resource optional
by Attila Király (JIRA) 20 Feb '13

20 Feb '13

Add possibility to mark included file/resource optional ------------------------------------------------------- Key: LBCORE-200 URL: http://jira.qos.ch/browse/LBCORE-200 Project: logback-core Issue Type: Improvement Components: Joran Affects Versions: 0.9.28 Reporter: Attila Király Assignee: Logback dev list Priority: Minor It would be nice if an <include /> element could be marked as optional. So if the file/resource is not found no error is logged about it (as it is now). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 1

[JIRA] (LOGBACK-794) If no config file is found, no debug info is printed
by Antony Stubbs (JIRA) 18 Feb '13

18 Feb '13

3 4

[JIRA] (LOGBACK-717) If no config file is found, no debug info is printed out, even with logback.debug=true sys prop
by Antony Stubbs (JIRA) 18 Feb '13

18 Feb '13

4 21