Phil Clay
Phil Clay
It's not clear to me why logstash-logback-encoder needs to provide _two_ extension points for customizing the writing of MDC entries: 1. override `MdcJsonProvider.writeMdcEntry` AND 2. custom implementation of `MdcEntryWriter` What...
Closing this in favor of using a custom `MdcEntryWriter`
Failing due to regression in mockito. https://github.com/mockito/mockito/issues/3019
@dependabot rebase
For anyone following this PR,... at present, we (the maintainers of logstash-logback-encoder) don't know how to generate, maintain, or test this file, so we cannot accept this PR as-is. Note...
What annotations? what libraries? What needs to be annotated? How do we test it with automation? Keep in mind I've never used GraalVM before, so explain it to me like...
I'd rather stick to the regexes. There are going to be tons of edge cases for generated classes that I do not think logstash-logback-encode should try to detect. We'll never...
Hi @diegomarquezp The marker classes are not currently designed to be consumed outside of logstash-logback-encoder. Backwards compatibility is not guarenteed for them. They are public only because the library needs...
@dependabot rebase
Until the version is bumped in logstash-logback-encoder, you can directly depend on the newer logback version in your application, or use dependencyManagement as described in [Including it in your project](https://github.com/logfellow/logstash-logback-encoder#including-it-in-your-project)