bump: slf4j 2.0.16, logback 1.5.7#32497
bump: slf4j 2.0.16, logback 1.5.7#32497sebastian-alfers merged 5 commits intoakka:mainfrom sebastian-alfers:bump-slf4-logback
Conversation
|
There's some docs that need updating as well: https://doc.akka.io/docs/akka/current/typed/logging.html#slf4j-api-compatibility |
Good point. I added a small correction to that part. But maybe we can even drop the entire "SLF4J API compatibility" section? |
Co-authored-by: Johan Andrén <johan@markatta.com>
patriknw
left a comment
patriknw
left a comment
There was a problem hiding this comment.
Can you also start a new migration page where we mention this dependency update.
https://github.com/akka/akka/tree/main/akka-docs/src/main/paradox/project
|
|
||
| It is however not possible to mix a logger backend supporting one version with SLF4J API of other version, that will lead | ||
| It is not possible to mix a logger backend supporting one version with SLF4J API of older versions, that will lead | ||
| to no logging to output like this: |
There was a problem hiding this comment.
Is below log message obsolete now? I don't think we want to encourage downgrading slf4j as is explained in below workaround.
There was a problem hiding this comment.
Yes, lets remove all the "working around this" docs.
|
Refs #32364 |
3 participants
Reverts the reflection based workaround introduced in #31825.