Thomas K

[slf4j-fcqn-issue-repro.zip](https://github.com/user-attachments/files/16613534/slf4j-fcqn-issue-repro.zip) actual output when I run it: ago 14, 2024 3:11:43 P. M. org.apache.logging.slf4j.SLF4JLogger logMessage INFORMACIÓN: this should be logged with org.example.Main, but isnt

the reality for us here across multiple libraries in one complex application is that many log frameworks are used. in our app we have code that uses all 3: jboss,...

> So there are 3 different indirections and you would like to preserve the caller path. correct. > probably a org.apache.logging.log4j:log4j-to-slf4j:2.20.0 issue I don't see how log4j-to-slf4j could have use...

a simpler, maybe more general reproducer, the problem also exists (i think because of the same reason / treatment of fqcn) when just using jboss -> slf4j bridge. here: with...

@ceki what do you think? is there consensus that this should be changed?

Hi all! Any update on the issue? anything that I can do to assist? cheers and thx

Is there a pre-release build somewhere to test? had troubles setting up / running maven locally on the repo :/ does it fix both reproducers attached here https://github.com/user-attachments/files/16613965/slf4j-fcqn-issue-repro2-direct.zip and further...

Ah ok, works now with mvn install. mvn compile didn't work at first. for info, error was: > INFO] Changes detected - recompiling the module! > [INFO] Compiling 1 source...

Just did local tests with the current master with the suggested fix: Fixes both reproducers and our actual prodution setup, which has a bit more stuff added on top! @ppkarwasz...

Hi all! do we have a decision regarding which approach we want to use, the one here or in https://github.com/qos-ch/slf4j/pull/439 ?