Bump jackson-bom from 2.14.2 to 2.15.0

[dependabot]

Bumps jackson-bom from 2.14.2 to 2.15.0.

Commits

• 2c28e23 [maven-release-plugin] prepare release jackson-bom-2.15.0
• 35c5c4f Prepare for 2.15.0 release
• 3fc3624 Back to snapshot deps
• 246b73c [maven-release-plugin] prepare for next development iteration
• c2b35ab [maven-release-plugin] prepare release jackson-bom-2.15.0-rc3
• 814d8f5 Prepare for 2.15.0-rc3 release
• 365ee6a Back to snapshot deps
• 2ff14f1 [maven-release-plugin] prepare for next development iteration
• 78c68bc [maven-release-plugin] prepare release jackson-bom-2.15.0-rc2
• 9f26bd4 Prepare for 2.15.0-rc2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sleberknight]

Among other things, this updates snakeyaml to 2.0.0 (which fixes a CVE). Also see the separate PR #584 which updates snakeyaml.

This should be tested in concert with the snakeyaml update against some (or all) of our projects before merging. Marking as Draft for now.

[sleberknight]

After running this against all our repositories, I found only one issue, which was in registry-aware-jersey-client, specifically in DropwizardClientsTest.AddJacksonMessageBodyProvider#shouldDeserializeJsonResponses. After some investigation it was caused by a change in Jackson because of Discrepancy in deserialization of ZonedDateTime and its associated fix in Normalize zone id during ZonedDateTime deserialization.

Once we update to Jackson 2.15.0 the above-mentioned test will fail, with the AssertJ error message:

org.opentest4j.AssertionFailedError: 
expected: DropwizardClientsTest.Person(id=42, firstName=Alice, lastName=Smith, [email protected], age=42, createdAt=2020-03-31T12:00Z[UTC], updatedAt=2020-11-15T14:30Z[UTC])
 but was: DropwizardClientsTest.Person(id=42, firstName=Alice, lastName=Smith, [email protected], age=42, createdAt=2020-03-31T12:00Z, updatedAt=2020-11-15T14:30Z)
Expected :DropwizardClientsTest.Person(id=42, firstName=Alice, lastName=Smith, [email protected], age=42, createdAt=2020-03-31T12:00Z[UTC], updatedAt=2020-11-15T14:30Z[UTC])
Actual   :DropwizardClientsTest.Person(id=42, firstName=Alice, lastName=Smith, [email protected], age=42, createdAt=2020-03-31T12:00Z, updatedAt=2020-11-15T14:30Z)

The specific problem is that the deserialized objects have date/time values such as 2020-03-31T12:00Z[UTC] while the expected ones have values like 2020-03-31T12:00Z. It's always a problem with certificates or time zones... 😄

One way to fix the test is to do this when creating the "expected" Person objects is to change the ZoneId.of("UTC") to ZoneOffset.UTC. Then the tests pass. Note that we cannot make this change until we update Jackson, because using ZoneOffset.UTC fails with Jackson 2.14.x.

Also see these references:

• Stack Overflow answer to "What is the difference between ZoneOffset.UTC and ZoneId.of("UTC")?"
• ZoneId#normalized (Java 8)
• ZoneId#normalized (Java 17)

[dependabot]

Superseded by #672.