[Jackson-3] Address #493, disable DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES by default.

[JooHyukKim]

addresses #493

Note

Once merged, JStep-2 Wiki should be updated.

[cowtowncoder]

@JooHyukKim Looks good, only had 1 comment that I added. I can change that & update release notes and then merge this.

[cowtowncoder]

Merged. Thank you @JooHyukKim !

[cowtowncoder]

@JooHyukKim Could you update JSTEP-2 page with change? I updated README, release-notes wiki.

[JooHyukKim]

@JooHyukKim Could you update JSTEP-2 page with change? I updated README, release-notes wiki.

Yes, for sure 👍🏼

Done 👍🏼

[cowtowncoder]

@JooHyukKim I think this broke a few tests in downstream packages (dataformats (binary, text, xml), jackson-modules-base etc). The reason it was not obvious was because snapshot builds started failing for 3.x few weeks ago -- I think api token I used got disabled for some reason. I created new one, assigned as secret, and snapshot deploys work again... and now breakage is obvious.

F.ex:

• jackson-modules-base: https://github.com/FasterXML/jackson-modules-base/actions/runs/10087808408

[cowtowncoder]

Fixed jackson-modules-base (2 tests for Afterburner, Blackbird, copied from jackson-databind).

Failing:

• jackson-dataformats-binary: https://github.com/FasterXML/jackson-dataformats-binary/actions/runs/10087812932
• jackson-dataformats-text: https://github.com/FasterXML/jackson-dataformats-text/actions/runs/10087815044
• jackson-dataformat-xml: https://github.com/FasterXML/jackson-dataformat-xml/actions/runs/10087817936
• Scala module: https://github.com/FasterXML/jackson-module-scala/actions/runs/10087826937

(and possibly others but these at least)

[JooHyukKim]

Oh okay, thanks! Will try to check on others as well

• File a PR in dataformats-text module
• File a PR in dataformats-xml module
• Struggling with dataformats-binary modules, I just keep flipping FAIL_ON_UNKNOWN_PROPERTIES feature back and forth 🤔

[JooHyukKim]

I wonder there is a way to alert cascading-build failure back to databind 🤔
Or if it should/shouldn't

[cowtowncoder]

@JooHyukKim in theory, there probably would be a way (cascading rebuild case could take some action). But for now email notifications probably need to suffice, as long as they get triggered. Although the problem here was not cascading part but snapshot deploy: both since new snapshot version was not made available and since this prevent cascading builds themselves (but without snapshot deploy they wouldn't have found issues either).

[cowtowncoder]

Ok so XML and text-formats fixed. Aside from binary-formats, Scala, 2 more failures:

• JAX-RS providers: https://github.com/FasterXML/jackson-jaxrs-providers/actions/runs/10097258838
• Jakarta-RS providers: https://github.com/FasterXML/jackson-jakarta-rs-providers/actions/runs/10097263912