- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-990) NPE when coloring stack trace sub-pattern with evaluator
by QOS.CH (JIRA) 29 Mar '17

29 Mar '17

1 0

[JIRA] (LOGBACK-1290) Logback don't have advice
by QOS.CH (JIRA) 25 Mar '17

25 Mar '17

xiaohu-zhang created LOGBACK-1290: ------------------------------------- Summary: Logback don't have advice Key: LOGBACK-1290 URL: https://jira.qos.ch/browse/LOGBACK-1290 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.3.0 Environment: operating system:windows softwar platform:eclipse Reporter: xiaohu-zhang Assignee: Logback dev list Priority: Minor Attachments: AdviceModel.java, ILogbackAdvice.java, Logger.java the logback do not have advice to enhance its input.for example:I want to add some message to all the logging message,their is no way to do so. I think it can be improve like this: 1.add class called AdviceModel.java in package ch.qos.logback.classic public class AdviceModel \{ private String msg; private String FQCN; private Level level; private Throwable throwable; } 2.add the interface in package ch.qos.logback.classic public interface ILogbackAdvice \{ default AdviceModel before(String localFQCN,String msg,Level level)\{ return null; } default void after(String localFQCN,String msg,Level level)\{ } default AdviceModel before(String localFQCN,String msg,Level level,Throwable t)\{ return null; } default void after(String localFQCN,String msg,Level level,Throwable t)\{ } } 3.modify the Logger.java like this: add field: private Map<ClassLoader,ILogbackAdvice> adviceMap = new ConcurrentHashMap<>(); add method: private ILogbackAdvice getAdvice()\{ if(adviceMap != null)\{ try \{ ILogbackAdvice adviceClassObject = adviceMap.get(Thread.currentThread().getContextClassLoader()); if(adviceClassObject == null)\{ Class<?> adviceClass = Thread.currentThread().getContextClassLoader().loadClass("LogbackAdvice"); adviceClassObject = (ILogbackAdvice)adviceClass.newInstance(); adviceMap.put(Thread.currentThread().getContextClassLoader(), adviceClassObject); } return adviceClassObject; } catch (ClassNotFoundException | InstantiationException | IllegalAccessException e) \{ // TODO Auto-generated catch block //there is no need for advicing do nothing adviceMap = null; } } return null; } then modify the method like error: public void error(String msg) \{ String fqcn = FQCN; Level level = Level.ERROR; String msgS = msg; ILogbackAdvice adviceClassObject = getAdvice(); if(adviceClassObject != null)\{ AdviceModel model = adviceClassObject.before(FQCN,msg,Level.ERROR); if(model != null)\{ String fqcns = model.getFQCN(); Level levels = model.getLevel(); String msgs = model.getMsg(); fqcn = fqcns != null ? fqcns:fqcn; level = levels != null ? levels:level; msgS = msgs != null ? msgs:msgS; } } filterAndLog_0_Or3Plus(fqcn, null, level, msgS, null, null); if(adviceClassObject != null)\{ adviceClassObject.after(FQCN,msg,Level.ERROR); } } I want to improve the logback and commit the branch fixed by me,Please Let me know if you think this improvement is ok(of course I used java8 version features,if i commit the code,i will use java6 version features). -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 9 EA Build 162 is available on java.net
by Rory O'Donnell 24 Mar '17

24 Mar '17

Hi Ceki, *JDK 9 Early Access* b162 <https://jdk9.java.net/download/> is available on java.net, summary of changes are listed here <http://download.java.net/java/jdk9/changes/jdk-9+162.html>. There is one fix for a bug reported by Open Source projects since the last availability email : * b161 - JDK 8176265 Method overload resolution on a covariant base type doesn't work in 9 Other change that maybe of interest: * b162 - JDK 8176503 security-libs Disable SHA-1 TLS Server Certificates *Better tools for adjusting to strong encapsulation -* please read Mark Reinhold's email on this topic [1] * * *Quality Outreach Report for March 2017 *is available [2], many thanks for your continued support and welcome to the new projects! ***Schedule - **JDK 9 Rampdown Phase 2*: Proposal accepted [3]. The overall goal of this process is to ensure that we fix just the bugs that must be fixed in order to ensure a successful release. Oracle's JRE and JDK Cryptographic Roadmap has been updated since last availability email [4] Rgds,Rory [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-March/011763.html [2] https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March… [3] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-March/005689.html [4] https://www.java.com/en/jre-jdk-cryptoroadmap.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1287) Breaking change? Custom appender can not be assigned to OutputStreamAppender
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

1 0

[JIRA] (LOGBACK-1287) Breaking change? Custom appender can not be assigned to OutputStreamAppender
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

1 0

[qos-ch/logback] bb39d1: LOGBACK-1287 fix II
by Ceki Gulcu 23 Mar '17

23 Mar '17

Branch: refs/heads/branch_1.2.3 Home: https://github.com/qos-ch/logback Commit: bb39d12342d911fd35c42e772438ebf427e46a75 https://github.com/qos-ch/logback/commit/bb39d12342d911fd35c42e772438ebf427… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-23 (Thu, 23 Mar 2017) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/encoder/LayoutWrappingEncoder.java Log Message: ----------- LOGBACK-1287 fix II

1 0

[JIRA] (LOGBACK-1287) Breaking change? Custom appender can not be assigned to OutputStreamAppender
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

1 0

[JIRA] (LOGBACK-1289) SizeAndTimeBasedRollingPolicy does not roll to the new date
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

1 0

[JIRA] (LOGBACK-1289) SizeAndTimeBasedRollingPolicy does not roll to the new date
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

1 0

[JIRA] (LOGBACK-1289) SizeAndTimeBasedRollingPolicy does not roll to the new date
by QOS.CH (JIRA) 23 Mar '17

23 Mar '17

Kathy Li created LOGBACK-1289: --------------------------------- Summary: SizeAndTimeBasedRollingPolicy does not roll to the new date Key: LOGBACK-1289 URL: https://jira.qos.ch/browse/LOGBACK-1289 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.2 Environment: logback version 1.2.2 Reporter: Kathy Li Assignee: Logback dev list Attachments: Capture.PNG, logback.xml I'm using the latest version of LOGBACK because it has the fix with the totalSizeCap in LOGBACK-1277 , however, now the log file does not know how to roll to the next day and the main log file disappear, you will see it is logging to multi tmp files all at once instead of the .txt I've attached the logback.xml and a screenshot of the log files inside the log folder. Can someone please give advice if it's a bug or some configuration I can do to fix that? thanks -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0