July 2018 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1375) Remove "final" designation on LoggerContext.getLogger(String)
by QOS.CH (JIRA) 07 Jul '18

07 Jul '18

1 0

[JIRA] (LOGBACK-1196) Add service loader to ContextSelectorStaticBinder.
by QOS.CH (JIRA) 07 Jul '18

07 Jul '18

1 0

[JIRA] (LOGBACK-1196) Add service loader to ContextSelectorStaticBinder.
by QOS.CH (JIRA) 06 Jul '18

06 Jul '18

1 0

[JIRA] (LOGBACK-1196) Add service loader to ContextSelectorStaticBinder.
by QOS.CH (JIRA) 06 Jul '18

06 Jul '18

1 0

[JIRA] (LOGBACK-1196) Add service loader to ContextSelectorStaticBinder.
by QOS.CH (JIRA) 06 Jul '18

06 Jul '18

1 0

[JIRA] (LOGBACK-1196) Add service loader to ContextSelectorStaticBinder.
by QOS.CH (JIRA) 06 Jul '18

06 Jul '18

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 04 Jul '18

04 Jul '18

1 0

JDK 11 is now in Rampdown Phase one
by Rory O'Donnell 02 Jul '18

02 Jul '18

Hi Ceki, *JDK 11 is now in Rampdown Phase one*** The overall feature set is frozen. No further JEPs will be targeted to this release.We’ve forked the main-line source repository, jdk/jdk, to the jdk/jdk11 stabilization repository. Any changes pushed to jdk/jdk or jdk/client are now bound for JDK 12. * For more details , see Mark Reinhold's email to jdk-dev mailing list [1] * The Rampdown Phase one process [2]. *Note: -* Early-Access build archive format on Windows has changed to zip. Since our last email the following JEPs have been targeted to JDK 11 : * 181: Nest-Based Access Control * 315: Improve Aarch64 Intrinsics * 330: Launch Single-File Source-Code Programs * 331: Low-Overhead Heap Profiling * 332: Transport Layer Security (TLS) 1.3 * 333: ZGC: A Scalable Low-Latency Garbage Collector (Experimental) * 335: *Deprecate the Nashorn JavaScript Engine* * 336: *Deprecate the Pack200 Tools and API* Other important changes since last email: Build 19: JDK-8205043 <https://bugs.openjdk.java.net/browse/JDK-8205043> : G1 enables adaptive parallel reference processing by default Build 18: JDK-8196141 <https://bugs.openjdk.java.net/browse/JDK-8196141> : Add GoDaddy root certificates JDK-8204243 <https://bugs.openjdk.java.net/browse/JDK-8204243> : *remove Thread.destroy() and Thread.stop(Throwable)* JDK-8202088 <https://bugs.openjdk.java.net/browse/JDK-8202088> : Japanese New Era Implementation Build 17: JDK-8189949 <https://bugs.openjdk.java.net/browse/JDK-8189949> : Remove Baltimore Cybertrust Code Signing CA JDK-8191031 <https://bugs.openjdk.java.net/browse/JDK-8191031> : Remove several Symantec Root CAs JDK-8072996 <https://bugs.openjdk.java.net/browse/JDK-8072996> : Deprecate stream-based GSSContext methods Build 16: JDK-8191844 <https://bugs.openjdk.java.net/browse/JDK-8191844> : Remove SECOM root Rgds, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001509.html [2] http://openjdk.java.net/projects/jdk/11/#Schedule

1 0

[JIRA] (LOGBACK-1411) Overwrite file contents when restarted
by QOS.CH (JIRA) 01 Jul '18

01 Jul '18

alinger created LOGBACK-1411: -------------------------------- Summary: Overwrite file contents when restarted Key: LOGBACK-1411 URL: https://jira.qos.ch/browse/LOGBACK-1411 Project: logback Issue Type: Bug Affects Versions: 1.2.3, 1.1.11 Environment: <?xml version="1.0" encoding="utf-8"?> <configuration> <property name="LOG_HOME" value="d:/imgtest/log"/> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <append>true</append> <Encoding>UTF-8</Encoding> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d\{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger\{50} - %msg%n</pattern> </layout> </appender> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <Encoding>UTF-8</Encoding> <file>$\{LOG_HOME}/log.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  <fileNamePattern>$\{LOG_HOME}/log-%d\{yyyy-MM-dd}.%i.log</fileNamePattern>  <maxFileSize>1MB</maxFileSize> <maxHistory>60</maxHistory> <totalSizeCap>1GB</totalSizeCap> </rollingPolicy> <encoder> <pattern>%d\{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger\{50} - %msg%n</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="STDOUT"/> <appender-ref ref="FILE"/> </root> </configuration> Reporter: alinger Assignee: Logback dev list When I use RollingFileAppender and SizeAndTimeBasedRollingPolicy to set <append>true</append> and <file>log.log</file> at the same time, but when I stop and restart on the same day, the original contents of the log.log file are emptied, but the original content does not generate a rolling file, and you can't find the original content anywhere. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0