October 2012 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-760) Failed to instantiate LoggerContext
by Jaroslav Holubec (JIRA) 10 Nov '12

10 Nov '12

2 1

[JIRA] (LOGBACK-725) Logging System fails silently when config filename has an unsupported extension
by Ryan Scheidter (JIRA) 09 Nov '12

09 Nov '12

3 3

[JIRA] Created: (LBCORE-209) Print configuration errors to stderr
by atomicknight (JIRA) 09 Nov '12

09 Nov '12

Print configuration errors to stderr ------------------------------------ Key: LBCORE-209 URL: http://jira.qos.ch/browse/LBCORE-209 Project: logback-core Issue Type: Improvement Components: Other Affects Versions: 0.9.28 Reporter: atomicknight Assignee: Logback dev list In org.slf4j.impl.StaticLoggerBinder#init(), any detected configuration errors are passed to StatusPrinter to be printed. However, the default PrintStream used by StatusPrinter is stdout, which can interfere with the output of command-line based Java programs that are used in the same fashion as applications such as ls or grep. Would it be possible to modify this behavior such that configuration errors are printed to stderr instead? A potential solution would be to overload StatusPrinter#printInCaseofErrorsOrWarning and StatusPrinter#printIfErrorsOccurred with versions that also take a PrintStream as an argument - this would allow classes like StaticLoggerBinder to specify the appropriate output stream without overriding the global state in StatusPrinter. Alternatively, an additional setting in the XML configuration might work just as well. -- 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

4 11

[JIRA] (LOGBACK-751) Configuration file specified by "logback.configurationFile" system property isn't applied when it doesn't have a .xml filename extension
by Libor Jelinek (JIRA) 08 Nov '12

08 Nov '12

3 3

[JIRA] (LOGBACK-766) Level.toLocationAwareLoggerInteger() has an unnecessary Level parameter
by Patrik Varga (JIRA) 31 Oct '12

31 Oct '12

1 1

[JIRA] (LOGBACK-728) XMLLayout does not escape &
by Gabriel Corona (JIRA) 30 Oct '12

30 Oct '12

2 4

[JIRA] Created: (LBCLASSIC-276) Add support for Throwable.getSuppressed()
by Joern Huxhorn (JIRA) 26 Oct '12

26 Oct '12

Add support for Throwable.getSuppressed() ----------------------------------------- Key: LBCLASSIC-276 URL: http://jira.qos.ch/browse/LBCLASSIC-276 Project: logback-classic Issue Type: New Feature Affects Versions: 0.9.29 Reporter: Joern Huxhorn Assignee: Logback dev list See http://old.nabble.com/Java-7-automatic-resource-management-and-suppressed-e… Java SE 7 adds a new feature to Throwable. http://www.oracle.com/technetwork/articles/java/trywithresources-401775.html explains this in detail. Relevant for us is the following new method: Throwable[] getSuppressed() It can optionally contain a list of Throwables that were suppressed by the new Java SE 7 try-with-resource functionality. We need to add support for that method be means of reflection. -- 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 4

[JIRA] (LOGBACK-749) Failed to get local hostname
by Oliver Schrenk (JIRA) 25 Oct '12

25 Oct '12

3 3

[JIRA] (LOGBACK-746) several NIO errors when using logback in tomcat
by Kireet Reddy (JIRA) 25 Oct '12

25 Oct '12

2 1

[JIRA] (LOGBACK-764) Allow context configuration through Java class
by Mark A. Ziesemer (JIRA) 25 Oct '12

25 Oct '12

1 0