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)

_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev

Reply via email to