FYI, AssertJ 4 is going to require Java 17, which would prevent us from testing on Java 8 and 11. We'll have to stay on the 3.x line, and I don't know how long it will be maintained once 4.0.0 is released. AssertJ also pulls in a newer version of byte-buddy than what we currently have through Mockito. Overall, I think it's a low-risk change. I'd be a bit more hesitant about rewriting all our Hamcrest usage, since that can introduce subtle test bugs. It can also make cherry-picking a chore.
On Sat, Jan 24, 2026 at 4:18 AM Oleg Kalnichevski <[email protected]> wrote: > Folks > > I have been meaning to do that literally for years. It really hurts > having to use the very basic Hamcrest matchers when working on > Httpcomponents. > > Are there any objections to adding AssertJ to core and eventually > replacing Hamcrest with AssertJ everywhere? > > Oleg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
