- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1480) SizeAndTimeBasedRollingPolicy stops working if name pattern includes several %d macroses
by QOS.CH (JIRA) 12 Aug '19

12 Aug '19

Aleksandr Golovin created LOGBACK-1480: ------------------------------------------ Summary: SizeAndTimeBasedRollingPolicy stops working if name pattern includes several %d macroses Key: LOGBACK-1480 URL: https://jira.qos.ch/browse/LOGBACK-1480 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3 Reporter: Aleksandr Golovin Assignee: Logback dev list Priority: Minor Create appended with following pattern: <fileNamePattern>logs/%d\{yyyy-MM-dd}/myApp-%d\{yyyy-MM-dd}-%d\{HH:mm:ss}.%i.log.gz</fileNamePattern> ER: Logs are being rolled out with AR: SizeAndTimeBasedRollingPolicy seem to stop working Please make it possible to use several %d macros +or+ explicitly mention in documentation that it's not supported. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/logback] 40788f: successful multi-release build
by Ceki Gulcu 12 Aug '19

12 Aug '19

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 40788f36eec7d4c3cdcb736c7ebbcd3f271e2c67 https://github.com/qos-ch/logback/commit/40788f36eec7d4c3cdcb736c7ebbcd3f27… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-12 (Mon, 12 Aug 2019) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml R logback-classic/src/main/java/module-info.java A logback-classic/src/main/java9/module-info.java M logback-core/pom.xml R logback-core/src/main/java/module-info.java A logback-core/src/main/java9/module-info.java M pom.xml Log Message: ----------- successful multi-release build Commit: b40f3de5f3a01179776f318da0f92092a600c3a1 https://github.com/qos-ch/logback/commit/b40f3de5f3a01179776f318da0f92092a6… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-12 (Mon, 12 Aug 2019) Changed paths: M README.md M logback-site/src/site/pages/setup.html Log Message: ----------- precision regarding build information Compare: https://github.com/qos-ch/logback/compare/976e35352174...b40f3de5f3a0

1 0

[qos-ch/logback] 40788f: successful multi-release build
by Ceki Gulcu 12 Aug '19

12 Aug '19

Branch: refs/heads/multirelease Home: https://github.com/qos-ch/logback Commit: 40788f36eec7d4c3cdcb736c7ebbcd3f271e2c67 https://github.com/qos-ch/logback/commit/40788f36eec7d4c3cdcb736c7ebbcd3f27… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-12 (Mon, 12 Aug 2019) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml R logback-classic/src/main/java/module-info.java A logback-classic/src/main/java9/module-info.java M logback-core/pom.xml R logback-core/src/main/java/module-info.java A logback-core/src/main/java9/module-info.java M pom.xml Log Message: ----------- successful multi-release build

1 0

JDK 13 is now in the Release Candidate Phase
by Rory O'Donnell 10 Aug '19

10 Aug '19

Hi Ceki, *JDK 13 is now in the Release Candidate Phase - if you are aware of any issues, please let us know. * Per the JDK 13 schedule [1], we are now in the Release Candidate phase. The stabilization repository, jdk/jdk13, is open for P1 bug fixes per the JDK Release Process (JEP 3) [2]. All changes require approval via the Fix-Request Process [3]. For more details, see Mark Reinhold's email to jdk-dev mailing list [4] * Milestone Schedule: o Initial RC Build 33 - Aug 9, 2019 o GAC - Aug 22, 2019 o GAR - Sept 5, 2019 o GA - Sept 17, 2019 *OpenJDK 13 build 33 is available at http://jdk.java.net/13/* * 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>. * Schedule, status & features o http://openjdk.java.net/projects/jdk/13/ * Release Notes o http://jdk.java.net/13/release-notes * Bug fixes reported by Open Source Projects : o JDK-8228764 - fixed in b32 -reported by Apache Tomcat **OpenJDK 14 *EA build 9 is now available at **http://jdk.java.net/14** * * 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>. * Release Notes o http://jdk.java.net/14/release-notes * JEPs targeted to JDK 14 o JEP 352 <http://openjdk.java.net/jeps/352> - Non-Volatile Mapped Byte Buffers * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B8%22%3A%3A…> * Bug fixes reported by Open Source Projects : o JDK-8227170 - fixed in b8 -reported by Apache Ant o JDK-8228485 - fixed in b8 -reported by JaCoCo o JDK-8222791 - fixed in b7 -reported by Apache Lucene *Project Panama Early-Access Builds* * Build jdk-14-panama+1-15 (2019/8/8) is available at http://jdk.java.net/panama/ * 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>. Regards, Rory [1] https://openjdk.java.net/projects/jdk/13/#Schedule [2] https://openjdk.java.net/jeps/3 [3] https://openjdk.java.net/jeps/3#Fix-Request-Process [4] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-August/003250.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1478) LogServiceProvider.initialize called twice
by QOS.CH (JIRA) 08 Aug '19

08 Aug '19

1 0

[JIRA] (LOGBACK-1478) LogServiceProvider.initialize called twice
by QOS.CH (JIRA) 07 Aug '19

07 Aug '19

1 0

[JIRA] (LOGBACK-1478) LogServiceProvider.initialize called twice
by QOS.CH (JIRA) 07 Aug '19

07 Aug '19

1 0

[JIRA] (LOGBACK-1478) LogServiceProvider.initialize called twice
by QOS.CH (JIRA) 07 Aug '19

07 Aug '19

Dan Groves created LOGBACK-1478: ----------------------------------- Summary: LogServiceProvider.initialize called twice Key: LOGBACK-1478 URL: https://jira.qos.ch/browse/LOGBACK-1478 Project: logback Issue Type: Bug Affects Versions: 1.3.0-alpha4 Reporter: Dan Groves Assignee: Logback dev list Attachments: logback-demo.tar With logback 1.3.0-alpha code and slf4j 1.8, {{LogServiceProvider::initialize}} can be called twice. I did not see this with logback 1.2.3 and slf4j 1.7.25. I attached some test code. The test code uses logback 1.3.0-alpha4, but I saw the problem with all alpha versions of logback 1.3.0. {noformat} $ tar xf logback-demo.tar $ cd logback-demo $ ./gradlew clean build BUILD SUCCESSFUL in 0s 8 actionable tasks: 7 executed, 1 up-to-date $ cd build/distributions $ tar xf logback-demo-1.0-SNAPSHOT.tar $ cd logback-demo-1.0-SNAPSHOT/bin/ $ ./logback-demo 16:30:12,127 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 16:30:12,127 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 16:30:12,127 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] 16:30:12,140 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@ee7d9f1 - URL [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] is not of type file 16:30:12,202 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 16:30:12,205 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 16:30:12,210 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 16:30:12,230 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 16:30:12,230 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 16:30:12,231 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 16:30:12,232 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@18ef96 - Registering current configuration as safe fallback point 16:30:12.233 [main] INFO demo - test 16:30:12,235 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 16:30:12,235 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 16:30:12,235 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] 16:30:12,235 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@17ed40e0 - URL [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] is not of type file 16:30:12,237 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 16:30:12,238 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 16:30:12,238 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 16:30:12,239 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 16:30:12,239 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 16:30:12,239 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 16:30:12,239 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@50675690 - Registering current configuration as safe fallback point {noformat} If I modify the {{build.gradle}} file in the bundle to comment out the newer dependencies and instead use the older ones, so that the dependencies block looks like: {noformat} dependencies { implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk8" // These cause the double call into LogbackServiceProvider.initialize // implementation "org.slf4j:slf4j-api:1.8.0-beta4" // implementation "ch.qos.logback:logback-classic:1.3.0-alpha4" // These do not cause the double call into LogbackServiceProvider.initialize implementation "org.slf4j:slf4j-api:1.7.25" implementation "ch.qos.logback:logback-classic:1.2.3" } {noformat} I get different output showing only one attempt to initialize logback: {noformat} $ ./gradlew clean build BUILD SUCCESSFUL in 0s 8 actionable tasks: 7 executed, 1 up-to-date $ cd build/distributions/ $ tar xf logback-demo-1.0-SNAPSHOT.tar $ cd logback-demo-1.0-SNAPSHOT/bin/ $ ./logback-demo 16:34:05,882 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 16:34:05,882 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 16:34:05,882 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] 16:34:05,894 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@ba8a1dc - URL [jar:file:/Users/dgroves/git/demo/logback-demo/build/distributions/logback-demo-1.0-SNAPSHOT/lib/logback-demo-1.0-SNAPSHOT.jar!/logback.xml] is not of type file 16:34:05,960 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 16:34:05,963 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 16:34:05,967 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 16:34:05,988 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 16:34:05,988 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 16:34:05,988 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 16:34:05,989 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4ca8195f - Registering current configuration as safe fallback point 16:34:05.991 [main] INFO demo - test {noformat} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/logback] 1068ad: Update configuration.html
by Ceki Gulcu 01 Aug '19

01 Aug '19

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 1068ad610eaa3383093042ed07a3644e908d1a78 https://github.com/qos-ch/logback/commit/1068ad610eaa3383093042ed07a3644e90… Author: Alan Thompson <cloojure(a)gmail.com> Date: 2019-07-31 (Wed, 31 Jul 2019) Changed paths: M logback-site/src/site/pages/manual/configuration.html Log Message: ----------- Update configuration.html small typo Commit: 976e35352174c3b222eaca69f3f447c2b4d4cd01 https://github.com/qos-ch/logback/commit/976e35352174c3b222eaca69f3f447c2b4… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-08-01 (Thu, 01 Aug 2019) Changed paths: M logback-site/src/site/pages/manual/configuration.html Log Message: ----------- Merge pull request #463 from cloojure/patch-1 Update configuration.html Compare: https://github.com/qos-ch/logback/compare/8fccc8879641...976e35352174

1 0

Investigation on the diffusion of innovation along with java releases
by Fernando Petrulio 31 Jul '19

31 Jul '19

Dear Developers, we are members of the ZEST research group (Zurich Empirical Software Engineering Team) based at the University of Zurich and the Delft University of Technology. We are conducting an investigation on the diffusion of innovations and we focus on the adoption of new language features. Our research is focused on how API producers adapt their interfaces to introduce support for Java 8’s lambdas. During the course of our investigation, we manually inspected logback-classic and logback-core’s source code and documentation to understand whether Java’s lambdas have widespread adoption. We would like to have your feedback on our findings. Our study focuses primarily on Functional Interfaces and Lambda Expressions as these new features were introduced by the Java language and adopted the Java JDK API, as they reduce implementation complexity, improve readability, offer performance benefits and improve security contextualization. Our analysis showed that LogBack 1.3 did not introduce compatibility with Java 8+ features, including Functional Interfaces and Lambda Expression. We would like to better understand as to why the API does not support newer Java language versions and their features. Our investigation showed us that in most cases API producers do not migrate their APIs to newer Java Releases. Despite this, the API remains to be widely used by consumers on GitHub. Can you provide us with more information on this phenomenon? Did you and your team ever discuss the migration to new Java releases? If so, what did this discussion entail? What is the reason behind not migrating to a newer Java version? Did the introduction of new language features such as lambda expressions influence your decision in any way? Does your API plan on introducing support for lambda expressions in the future? We thank you for taking the time to answer our questions. If you would like to be posted about the results of this study, please let us know! Kind Regards, Fernando Petrulio. -- Fernando Petrulio Ph.D. Student - University of Zurich UZH Department of Informatics fpetrulio(a)ifi.uzh.ch

1 0