Matt Nelson

Does adding a non-default/higher priority on the custom provider take precedence over the dropwizard registered instance? https://jakarta.ee/specifications/platform/8/apidocs/javax/annotation/priority

> In the [Jersey docs](https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest/message-body-workers.html#providers-selection) the selection algorithm doesn't specify it would handle `@Priority` annotations. I suggested it based on this comment > https://github.com/eclipse-ee4j/jersey/issues/3473#issuecomment-460624390

I am using the extended forms to bypass using Prefixed converters. I would like to keep that option.

My recommendation would be to introduce new dropwizard specific conversion words so that all the standard logback conversion words[1] work as documented, which is where the configuration docs[2] defer to....

> I think that would have been the best way to go in early versions of Dropwizard. Now it feels like a behavior change that could be confusing. I realize...

Any updates on when a resolution will be available? There might be an influx of attention to this issue with the recent git CVE. https://github.blog/2021-03-09-git-clone-vulnerability-announced/

> Another issue with directly depending on the original project is that it brings in a transitive dependency on commons collections. Part of the motivation for the fork seems to...

> guava/commons-collections4 are removed in 0.4.0 via [flipkart-incubator/zjsonpatch#60](https://github.com/flipkart-incubator/zjsonpatch/pull/60) looks like common-collections4 worked its way back in https://github.com/flipkart-incubator/zjsonpatch/blame/master/pom.xml#L149

Seeing this same issue occasionally. I have a large reactor that is building in parallel. Due the randomness of the failures, my hunch is that this is a concurrency issue....

> * [ ] I tested my code in Kubernetes Are there more docs on the expectations of the k8s testing cluster? https://github.com/fabric8io/kubernetes-client/blob/master/CONTRIBUTING.md#check-your-work-after-running-all-unit-and-regression-tests