- logback-dev - mailman3.qos.ch

[qos-ch/logback] 7b02b1: ongoing work on LOGBACK-1415
by Ceki Gulcu 14 Aug '18

14 Aug '18

Branch: refs/heads/branch_1.2.x Home: https://github.com/qos-ch/logback Commit: 7b02b1bf465e4062b53f9cf027d2323a64b14f14 https://github.com/qos-ch/logback/commit/7b02b1bf465e4062b53f9cf027d2323a64… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-08-14 (Tue, 14 Aug 2018) Changed paths: A logback-classic/src/main/java/ch/qos/logback/classic/pattern/PrefixCompositeConverter.java Log Message: ----------- ongoing work on LOGBACK-1415 **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.

1 0

[JIRA] (LOGBACK-1415) {{prefix}} composite converter
by QOS.CH (JIRA) 14 Aug '18

14 Aug '18

Ceki Gülcü created LOGBACK-1415: ----------------------------------- Summary: {{prefix}} composite converter Key: LOGBACK-1415 URL: https://jira.qos.ch/browse/LOGBACK-1415 Project: logback Issue Type: Improvement Reporter: Ceki Gülcü Assignee: Logback dev list In order to help output parsers, it is sometimes useful to prefix log output with the key of each item. *Example 1:* {code}%X{user} {code} would be easier to parse if it were written as {code}%X{user} {code} *Example 2:* {code}%X{user} %{sessionId} %level %logger %msg{code} would be easier to parse if written as {code}user=%X{user} sessionId=%{sessionId} level=%level logger=$logger msg=%msg}{code} The {{prefix}} composite converter automates the process. Thus, the following patterns generate equivalent output {code}%prefix(%X{user} %{sessionId} %level %logger %msg){code} and {code}user=%X{user} sessionId=%{sessionId} level=%level logger=$logger msg=%msg}{code} {code}user=%X{user} sessionId=%{sessionId} level=%level logger=$logger msg=%msg}{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1344) RollingCalendar invalid "period barrier crossed" computation
by QOS.CH (JIRA) 09 Aug '18

09 Aug '18

1 0

[JIRA] (LOGBACK-1414) Make configurable MDC keys in MDCInsertingServletFilter
by QOS.CH (JIRA) 08 Aug '18

08 Aug '18

Daisuke Miyamoto created LOGBACK-1414: ----------------------------------------- Summary: Make configurable MDC keys in MDCInsertingServletFilter Key: LOGBACK-1414 URL: https://jira.qos.ch/browse/LOGBACK-1414 Project: logback Issue Type: Improvement Components: logback-classic Environment: As MDC keys used by MDCInsertingServletFilter is hard-coded in ClassicConstants, we cannot configure these key names. My application have a problem that the key should not contain period (.) Reporter: Daisuke Miyamoto Assignee: Logback dev list Priority: Minor -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 11 , JDK 12 and JDK 8u192 Early Access builds are available on jdk.java.net
by Rory O'Donnell 07 Aug '18

07 Aug '18

Hi Ceki, *JDK 11 Early Access build 25 is available at : - **jdk.java.net/11/* * *JDK 11 entered Rampdown Phase 2 on 26-July [1]* o The overall feature set is frozen. No further JEPs will be targeted to this release. o We now turn our focus to P1 and P2 bugs. * Release notes are available here [2] *JDK 12 Early Access build 05 is available at : - **jdk.java.net/12/* * Changes in this build here <http://hg.openjdk.java.net/jdk/jdk/log?revcount=10000&rev=reverse%28%22jdk-…>. *JDK 8u192 Early Access build 04 is available at : - http://jdk.java.net/8/* * JDK 8u192 timeline is available [3] o GA is scheduled for October 2018 **Conference videos online* * * *OpenJDK Committers’ Workshop [4]* * JVM Language Summit 2018 [5]: Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-July/001669.html [2] http://jdk.java.net/11/release-notes [3] http://openjdk.java.net/projects/jdk8u/releases/8u192.html [4] https://www.youtube.com/playlist?list=PLX8CzqL3ArzXY_9Ornabhxs-j2h4hnvJ3 [5] https://www.youtube.com/playlist?list=PLX8CzqL3ArzVnxC6PYxMlngEMv3W1pIkn -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 05 Aug '18

05 Aug '18

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 05 Aug '18

05 Aug '18

1 0

[JIRA] (LOGBACK-1413) 1.3.0-alpha4 LoggerContext's ExecutorService no longer executes
by QOS.CH (JIRA) 02 Aug '18

02 Aug '18

paul hinds created LOGBACK-1413: ----------------------------------- Summary: 1.3.0-alpha4 LoggerContext's ExecutorService no longer executes Key: LOGBACK-1413 URL: https://jira.qos.ch/browse/LOGBACK-1413 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha4 Environment: Windows 10, Java 8, Running in JUnit tests in IntelliJ Reporter: paul hinds Assignee: Logback dev list LoggerContext provides an ExecutorService. I am using this to start a TCP appender similar to the one provided by logback. {{Context context = {color:#cc7832}new {color}LoggerContext(){color:#cc7832};{color}ExecutorService ses = context.getExecutorService(){color:#cc7832};{color}ses.submit(() -> System.{color:#9876aa}out{color}.println({color:#6a8759}"ScheduledExecutorService running"{color})){color:#cc7832};{color}}} {color:#cc7832}Would print the text.{color} {color:#cc7832}Running with 1.3.0-alpha4 version, the lambda is no longer executed{color} {color:#cc7832}N.B. context.getExecutorService() has been deprecated the same applies to context.getScheduledExecutorService(){color} {color:#cc7832} {color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-112) classloader for loading autoConfig configuration resource
by QOS.CH (JIRA) 31 Jul '18

31 Jul '18

1 0

[JIRA] (LOGBACK-204) file appender that rolls on startup
by QOS.CH (JIRA) 26 Jul '18

26 Jul '18

1 0