[slf4j-dev] [JIRA] Updates for SLF4J-533: Add support for {{LocationAwareLogger}} to {{DefaultLoggingEventBuilder}}'s fallback path

[QOS.CH (JIRA)]

SLF4J / SLF4J-533 [Open]
Add support for {{LocationAwareLogger}} to {{DefaultLoggingEventBuilder}}'s fallback path

==============================

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/SLF4J-533

==============================
 Issue created
------------------------------

ExE Boss created this issue on 07/Jan/22 11:15 PM
Summary:              Add support for {{LocationAwareLogger}} to {{DefaultLoggingEventBuilder}}'s fallback path
Issue Type:           Bug
Affects Versions:     2.0.0-alpha5, 2.0.0-alpha6
Assignee:             SLF4J developers list
Components:           Core API
Created:              07/Jan/22 11:15 PM
Priority:             Major
Reporter:             ExE Boss
Description:
  Currently, if a [{{LocationAwareLogger}}|https://www.slf4j.org/api/org/slf4j/spi/LocationAwareLogger.html] doesn't also implement [{{LoggingEventAware}}|https://www.slf4j.org/api/org/slf4j/spi/LoggingEventAware.html], then {{DefaultLoggingEventBuilder}} discards caller boundary information, even though [{{LocationAwareLogger::log}}|https://www.slf4j.org/api/org/slf4j/spi/LocationAwareLogger.html#log(org.slf4j.Marker,java.lang.String,int,java.lang.String,java.lang.Object%5B%5D,java.lang.Throwable)] accepts a {{fqcn}} parameter.
  
  h2. Success metrics
  {{DefaultLoggingEventBuilder}} correctly passes caller boundary information to {{LocationAwareLogger::log}}.


==============================
 This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)