Skip to content

Consistently use slf4j/log4j bridge (#139226)#139952

Merged
elasticsearchmachine merged 6 commits intoelastic:8.19from
rjernst:logging/slf4j_bridge_8.19
Dec 29, 2025
Merged

Consistently use slf4j/log4j bridge (#139226)#139952
elasticsearchmachine merged 6 commits intoelastic:8.19from
rjernst:logging/slf4j_bridge_8.19

Conversation

@rjernst
Copy link
Copy Markdown
Member

@rjernst rjernst commented Dec 23, 2025

Some 3rd party dependencies use SLF4J but Elasticsearch internally uses log4j. Historically there were problems with using the log4j adapter for SLF4J, but those have gone away with the removal of SecurityManager. This commit updates uses of slf4j to consistently use the log4j bridge.

closes #137556

Some 3rd party dependencies use SLF4J but Elasticsearch internally uses
log4j. Historically there were problems with using the log4j adapter for
SLF4J, but those have gone away with the removal of SecurityManager.
This commit updates uses of slf4j to consistently use the log4j bridge.

closes elastic#137556

Co-authored-by: David Turner <david.turner@elastic.co>
@rjernst rjernst added backport auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) labels Dec 23, 2025
@elasticsearchmachine elasticsearchmachine merged commit 2a0a1ae into elastic:8.19 Dec 29, 2025
29 checks passed
@rjernst rjernst deleted the logging/slf4j_bridge_8.19 branch December 29, 2025 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.19.10

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants