yes, such conflicts are unfortunate, but java devs...
# stdlib
m
yes, such conflicts are unfortunate, but java devs have to handle them anyway, as no libraries i'm aware of have a "we will not add members to existing classes" policy. the fix, as long as newer version is backwards compatible with old, is just to use maven/gradle to forcibly pin the dependency graph to a single version