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

[JIRA] Updates for LOGBACK-1531: Total size cap does not cover all history
by QOS.CH (JIRA) 28 Oct '20

28 Oct '20

logback / LOGBACK-1531 [Open] Total size cap does not cover all history ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1531 ============================== Issue created ------------------------------ Max created this issue on 28/Oct/20 1:14 PM Summary: Total size cap does not cover all history Issue Type: Bug Assignee: Logback dev list Components: logback-core Created: 28/Oct/20 1:14 PM Environment: Indifferent Priority: Minor Reporter: Max Description: There is an off by one error in the total size cap logic which means that it does not delete files from the oldest period when trying to limit size. This means that if logs are present for all (max history) periods the total size cap is not respected. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1531) Total size cap does not cover all history
by QOS.CH (JIRA) 28 Oct '20

28 Oct '20

1 0

JDK 16 EA build 21 is available
by Rory O'Donnell 23 Oct '20

23 Oct '20

Hi Ceki, OpenJDK 16 Early Access build 21**is now available at http://jdk.java.net/16 * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Schedule (proposed) 2020/12/10 Rampdown Phase One 2021/01/14 Rampdown Phase Two 2021/02/04 Initial Release Candidate 2021/02/18 Final Release Candidate 2021/03/16 General Availability * Features: o JEPs targeted to JDK 16, so far: + JEP 338: Vector API (Incubator) <https://openjdk.java.net/jeps/338> + JEP 347: Enable C++14 Language Features <https://openjdk.java.net/jeps/347> + JEP 357: Migrate from Mercurial to Git <https://openjdk.java.net/jeps/357> + JEP 369: Migrate to GitHub <https://openjdk.java.net/jeps/369> + JEP 376: ZGC: Concurrent Thread-Stack Processing <https://openjdk.java.net/jeps/376> + JEP 386: Alpine Linux Port <https://openjdk.java.net/jeps/386> + JEP 387: Elastic Metaspace <https://openjdk.java.net/jeps/387> + JEP 388: Windows/AArch64 Port <https://openjdk.java.net/jeps/388> ** * Changes in recent builds that maybe of interest: o Build 21 + JDK-8236862: Enhance support of Proxy class + JDK-8237990: Added Property to Control LDAP Authentication Mechanisms Allowed to Authenticate Over Clear Connections + JDK-8242068: Signed JAR support for RSASSA-PSS and EdDSA + JDK-8245417: Improve certificate chain handling + JDK-8253952: Refine ZipOutputStream.putNextEntry() to recalculate ZipEntry's compressed size o Build 20 + JDK-8232092: (fs) Files::isWritable returns false on a writeable root directory (win) # Reported by JUnit5 + JDK-8248262: Wrong link target in ModuleDescriptor#isAutomatic's API documentation # Reported by JUnit5 + JDK-8253965: Delete the outdated java.awt.PeerFixer class + JDK-8253566: clazz.isAssignableFrom will return false for interface implementors # Found by Hibernate Validator + JDK-8254177: US/Pacific-New Zone name removed as part of tzdata2020b o Build 19 + JDK-8253761: Wrong URI syntax printed by jar --describe-module # Reported by JUnit5 Project Lanai Early-Access Build: EA 6 Build 16-lanai+2-229 <http://jdk.java.net/lanai/> (2020/10/4) * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * These builds are based upon the latest state of the current in development JDK, and so may contain new features and unresolved bugs unrelated to Project Lanai. Project Lanai Wiki: https://wiki.openjdk.java.net/display/lanai/Main * Please send feedback via e-mail tolanai-dev(a)openjdk.java.net <mailto:lanai-dev@openjdk.java.net>. To send e-mail to this address you must firstsubscribe to the mailing list <https://mail.openjdk.java.net/mailman/listinfo/lanai-dev>. Project Panama Early-Access Build: Build 16-panama+2-193 <http://jdk.java.net/panama/> (2020/10/1) * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * These builds are based on an incomplete version of JDK 16. * Please send feedback via e-mail topanama-dev(a)openjdk.java.net <mailto:panama-dev@openjdk.java.net>. To send e-mail to this address you must firstsubscribe to the mailing list <http://mail.openjdk.java.net/mailman/listinfo/panama-dev>. Oracle JRE and JDK Cryptographic Roadmap has been updated [1] * Oracle has announced plans to add support for x25519 and x448 named elliptic curve groups to TLS. * Support is targeted for JDK 11 with the January 2021 CPU release. Oracle Critical Patch Update released 21-Oct-2020 * https://www.oracle.com/security-alerts/cpuoct2020.html *__* Rgds,Rory [1] https://java.com/en/jre-jdk-cryptoroadmap.html -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-857) Inheritance across multiple logback.xml files
by QOS.CH (JIRA) 22 Oct '20

22 Oct '20

1 0

[JIRA] Updates for LOGBACK-1530: Fluent Logging no longer works with 1.3.0-alpha5
by QOS.CH (JIRA) 16 Oct '20

16 Oct '20

logback / LOGBACK-1530 [Open] Fluent Logging no longer works with 1.3.0-alpha5 ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1530 ============================== Issue created ------------------------------ Daniel Johnson created this issue on 16/Oct/20 7:48 PM Summary: Fluent Logging no longer works with 1.3.0-alpha5 Issue Type: Bug Affects Versions: 1.3.0-alpha5 Assignee: Logback dev list Components: logback-classic Created: 16/Oct/20 7:48 PM Environment: slf4j:2.0.0-alpha1, logback-classic:1.3.0-alpha5 Priority: Major Reporter: Daniel Johnson Description: Fluent logging results in no-op logging with Logback 1.3.0-alpha5, due to what is seemingly an unnecessary override in _ch/qos/logback/classic/Logger.java_ class that points to a no-op implementation for the _LoggingEventBuilder_: {code:java} @Override public LoggingEventBuilder makeLoggingEventBuilder(org.slf4j.event.Level level) { return new LogbackLoggingEventBuilder(this, level); } {code} The _LogbackLoggingEventBuilder_ class is all no-op methods with TODO markers, which was added in a commit last August with commit message "ongoing work". Based on my _very_ limited understanding, SLF4J 2.0 provides a default implementation for this method, and Logback does not need to override it. By switching back to Logback 1.3.0-alpha4, fluent logging works as expected. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1502) Janino no longer works with 1.3.0-alpha5
by QOS.CH (JIRA) 16 Oct '20

16 Oct '20

1 0

[qos-ch/logback-decoder] de977a: Bump junit from 4.8.2 to 4.13.1
by dependabot[bot] 12 Oct '20

12 Oct '20

Branch: refs/heads/dependabot/maven/junit-junit-4.13.1 Home: https://github.com/qos-ch/logback-decoder Commit: de977a17aecf729ab0dac48baa130502a4b28390 https://github.com/qos-ch/logback-decoder/commit/de977a17aecf729ab0dac48baa… Author: dependabot[bot] <49699333+dependabot[bot](a)users.noreply.github.com> Date: 2020-10-12 (Mon, 12 Oct 2020) Changed paths: M pom.xml Log Message: ----------- Bump junit from 4.8.2 to 4.13.1 Bumps [junit](https://github.com/junit-team/junit4) from 4.8.2 to 4.13.1. - [Release notes](https://github.com/junit-team/junit4/releases) - [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4… - [Commits](https://github.com/junit-team/junit4/compare/r4.8.2...r4.13.1) Signed-off-by: dependabot[bot] <support(a)github.com>

1 0

[JIRA] Updates for LOGBACK-1529: How to limit the number of log files per day
by QOS.CH (JIRA) 12 Oct '20

12 Oct '20

logback / LOGBACK-1529 [Open] How to limit the number of log files per day ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1529 ============================== Issue created ------------------------------ Tamil Mani created this issue on 12/Oct/20 12:17 PM Summary: How to limit the number of log files per day Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Components: logback-classic, logback-core Created: 12/Oct/20 12:17 PM Environment: How to limit number of log files per day. I need to handle file size and no of files per day. Labels: SizeAndTimeBasedRollingPolicy TimeBasedRollingPolicy logging rollingFileappender Priority: Major Reporter: Tamil Mani Description: Please refer this [https://stackoverflow.com/questions/9101627/how-to-limit-the-number-of-file…] ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1465) xxe vulnerability in Logback
by QOS.CH (JIRA) 09 Oct '20

09 Oct '20

1 0

[JIRA] (LOGBACK-1489) with SizeAndTimeBasedRollingPolicy totalSizeCap cannot be smaller than maxFileSize
by QOS.CH (JIRA) 05 Oct '20

05 Oct '20

1 0