Update dropwizard3 to use logback13, correct logback13 issues#115
Merged
Conversation
jtduffy
approved these changes
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
dropwizard3to use thelogback13extension instead oflogback. (logbackdid appear to be compatible with the newer versions of the module, but better to keep logback dependencies roughly aligned).In the process, I found a couple things in the logback13 module that I fixed here as well to make it consistent with vanilla logback:
NewRelic:prefix should be stripped off our metadata log attributes before they're written to the generator-Dnewrelic.log_extensions.add_mdc=false).