- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-624) MDC Adapter with configurable InheritableThreadLocal
by QOS.CH (JIRA) 13 Sep '17

13 Sep '17

1 0

Moving Java Forward Faster
by Rory O'Donnell 07 Sep '17

07 Sep '17

Hi Ceki, Oracle is proposing a rapid release model for Java SE going-forward. The high points are highlighted below, details of the changes can be found on Mark Reinhold’s blog [1] , OpenJDK discussion email list [2]. Under the proposed release model, after JDK 9, we will adopt a strict, time-based model with a new major release every six months, update releases every quarter, and a long-term support release every three years. The new JDK Project will run a bit differently than the past "JDK $N" Projects: - The main development line will always be open but fixes, enhancements, and features will be merged only when they're nearly finished. The main line will be Feature Complete [3] at all times. - We'll continue to use the JEP Process [4] for new features and other significant changes. The bar to target a JEP to a specific release will, however, be higher since the work must be Feature Complete in order to go in. Owners of large or risky features will be strongly encouraged to split such features up into smaller and safer parts, to integrate earlier in the release cycle, and to publish separate lines of early-access builds prior to integration. The JDK Updates Project will run in much the same way as the past "JDK $N" Updates Projects, though update releases will be strictly limited to fixes of security issues, regressions, and bugs in newer features. Related to this proposal, we intend to make a few changes in what we do: - Starting with JDK 9 we'll ship OpenJDK builds under the GPL [5], to make it easier for developers to deploy Java applications to cloud environments. We'll initially publish OpenJDK builds for Linux/x64, followed later by builds for macOS/x64 and Windows/x64. - We'll continue to ship proprietary "Oracle JDK" builds, which include "commercial features" [6] such as Java Flight Recorder and Mission Control [7], under a click-through binary-code license [8]. Oracle will continue to offer paid support for these builds. - After JDK 9 we'll open-source the commercial features in order to make the OpenJDK builds more attractive to developers and to reduce the differences between those builds and the Oracle JDK. This will take some time, but the ultimate goal is to make OpenJDK and Oracle JDK builds completely interchangeable. - Finally, for the long term we'll work with other OpenJDK contributors to establish an open build-and-test infrastructure. This will make it easier to publish early-access builds for features in development, and eventually make it possible for the OpenJDK Community itself to publish authoritative builds of the JDK. Questions , comments, feedback to OpenJDK discuss mailing list [2] Rgds,Rory [1]https://mreinhold.org/blog/forward-faster [2]http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html [3]http://openjdk.java.net/projects/jdk8/milestones#Feature_Complete [4]http://openjdk.java.net/jeps/0 [5]http://openjdk.java.net/legal/gplv2+ce.html [6]http://www.oracle.com/technetwork/java/javase/terms/products/index.html [7]http://www.oracle.com/technetwork/java/javaseproducts/mission-control/ind… [8]http://www.oracle.com/technetwork/java/javase/terms/license/index.html

1 0

[JIRA] (LOGBACK-1106) There is no conversion class registered for conversion word [d]
by QOS.CH (JIRA) 01 Sep '17

01 Sep '17

1 0

[JIRA] (LOGBACK-1214) Every night after the use of the log scroll compression, there is no release of the handle
by QOS.CH (JIRA) 31 Aug '17

31 Aug '17

1 0

[JIRA] (LOGBACK-1322) File handles to tmp file kept open after rotation
by QOS.CH (JIRA) 31 Aug '17

31 Aug '17

1 0

[JIRA] (LOGBACK-1339) log4j properties translator page is down
by QOS.CH (JIRA) 27 Aug '17

27 Aug '17

1 0

[JIRA] (LOGBACK-1339) log4j properties translator page is down
by QOS.CH (JIRA) 27 Aug '17

27 Aug '17

1 0

[JIRA] (LOGBACK-1339) log4j properties translator page is down
by QOS.CH (JIRA) 25 Aug '17

25 Aug '17

ArunKumar Srinivasan created LOGBACK-1339: --------------------------------------------- Summary: log4j properties translator page is down Key: LOGBACK-1339 URL: https://jira.qos.ch/browse/LOGBACK-1339 Project: logback Issue Type: Bug Components: logback-site Environment: [https://logback.qos.ch/translator/] is broken Reporter: ArunKumar Srinivasan Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1338) SizeAndTimeBasedRollingPolicy do not delete the old files
by QOS.CH (JIRA) 24 Aug '17

24 Aug '17

seenimurugan shanmugam created LOGBACK-1338: ----------------------------------------------- Summary: SizeAndTimeBasedRollingPolicy do not delete the old files Key: LOGBACK-1338 URL: https://jira.qos.ch/browse/LOGBACK-1338 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.1.10 Reporter: seenimurugan shanmugam Assignee: Logback dev list I configured the archive file structure as specified by the below configuration <appender name="SCHEDULER" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>$\{LOG_HOME}/scheduler.log</File> <encoder> <pattern>%d %p [%t] [%X\{serviceName}] [%X\{username}] %X\{someOtherName} %logger\{10} - %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>$\{LOG_HOME}/archive/%d\{yyyy/MM/dd}/scheduler.%i.log.gz</fileNamePattern> <maxHistory>5</maxHistory> <totalSizeCap>2GB</totalSizeCap> <maxFileSize>50MB</maxFileSize> </rollingPolicy> </appender> The date and time is not attached to the file name but folder is created for each day. This does not delete the old files above 5 days old. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1337) LogbackMDCAdapter should store mdc in LinkedHashMap to predict order of MDC in %X
by QOS.CH (JIRA) 24 Aug '17

24 Aug '17

Martin Walsh created LOGBACK-1337: ------------------------------------- Summary: LogbackMDCAdapter should store mdc in LinkedHashMap to predict order of MDC in %X Key: LOGBACK-1337 URL: https://jira.qos.ch/browse/LOGBACK-1337 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.2.3, 1.1.11 Reporter: Martin Walsh Assignee: Logback dev list LogbackMDCAdapter uses HashMap rather than LinkedHashMap and so the order of the key value pairs when logging MDC with %X cannot be predicted from one log line to another. This makes log parsing harder than it has to be. Using LinkedHashMap would address this as the order of adding to MDC would be preserved. See [https://github.com/qos-ch/logback/blob/v_1.2.3/logback-classic/src/main/jav…] & https://github.com/qos-ch/logback/blob/v_1.1.11/logback-classic/src/main/ja… -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0