investigate major binary compatibility regressions caused by jackson-databind 2.15.0-rc3-SNAPSHOT

[pjfanning]

investigate major binary compatibility regressions caused by jackson-databind 2.15.0-rc3-SNAPSHOT

[pjfanning]

It's not that we use the methods. The build checks for API changes and when we subclass, the build will fail if methods are removed in the super classes. These checks can be configured to ignore certain diffs and I've now done that.

[pjfanning]

I fixed the build issue with ae65569

[cowtowncoder]

@pjfanning Ok sorry about that. I had assumed that all modules would have long ago switched not to use those methods -- and also rebuilt core modules. But I forgot that I do not do this for Scala module.

And I should also know better than to start cleanup after second release candidate. In future I will postpone these appropriately.

Thank you for catching this so quickly.

[cowtowncoder]

Ok good. Kotlin module does something similar, makes sense.

Might make sense for databind too, although one concern I have is with sheer number of overrides needed for "internal" changes (in theory any change to any protected methods is backwards-incompatible change). The idea is valid tho, it is important to be aware of such changes to avoid accidental removal/change of methods.