David M. Lloyd
David M. Lloyd
@dependabot recreate
At this point, we might as well wait for 2.5.0.
If you're referring to https://github.com/jbossas/jboss-threads/issues/139 then yes it was fixed.
I like the idea of this change (note that a few of the APIs I have added to this project in the past also use this pattern, and the new...
This is a good question that I do not have an answer to. Maybe start with a high-level proposal that encompasses the existing API usages for method, class, and block...
Given that ResultType is an enum (i.e. immutable and thus relatively foolproof), IMO it's probably OK to just make it public.
We could make that public too I think. At least I see no reason why not.
https://github.com/junit-team/junit5/releases/tag/r5.10.3 🎉
Yeah it should include the backport we need.
Could it be that `RuntimeUpdatesProcessor` is getting duplicated onto both class loaders, and it's the "wrong one" being accessed? Or something along those lines?