In io.quarkus.jackson.ObjectMapperCustomizer, use JsonMapper.Builder instead of ObjectMapper

[chonton]

Closes #24019

[chonton]

Probably merge conflicts with #23995. (Are you ready to merge that?)

[quarkus-bot]

Failing Jobs - Building 2ec31af

Status	Name	Step	Failures	Logs	Raw logs
✖	Devtools Tests - JDK 11	Build	Failures	Logs	Raw logs
✖	Devtools Tests - JDK 17	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Devtools Tests - JDK 11 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

✖ io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

---

⚙️ Devtools Tests - JDK 17 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

✖ io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

[gastaldi]

We can't break compatibility because injecting ObjectMapper is used a lot.

I suggest maintaining the same behavior by deprecating it and introduce the new enhancement

[gastaldi]

Also how would that work for non-json content?

[gsmet]

Yeah, this is a good start but we need to think about the proper strategy to make that change as we don't want to break all the applications around.

[chonton]

These changes should be backwards compatible. JsonMapper is an ObjectMapper. There is backwards compatibility for invoking the deprecated ObjectMapperCustomizer(s) provided by non-quarkus managed code.

@gastaldi, what do you mean by non-json content? Is there current or future support for any other text mappers such as YamlMapper? Support for any binary mappers such as AvroMapper?

[gastaldi]

@chonton I don't think we do that now, but an ObjectMapperCustomizer instance could work on any ObjectMapper implementation (eg. YAMLMapper).

[chonton]

When XxxMapper is introduced, is it better to use a single Customizer interface, or specific XxxCustomizer per XxxMapper?

[gastaldi]

When XxxMapper is introduced, is it better to use a single Customizer interface, or specific XxxCustomizer per XxxMapper?

IMHO a single Customizer interface would be easier, as it does not require any code changes when a new ObjectMapper implementation is introduced