Skip to content

Conversation

@IvanPuntev
Copy link
Contributor

@IvanPuntev IvanPuntev commented Sep 21, 2025

Feature / fix #305 and #242
Obsolete #306

@IvanPuntev IvanPuntev requested a review from a team as a code owner September 21, 2025 17:37
@IvanPuntev
Copy link
Contributor Author

@SlyngDK please review.

@IvanPuntev
Copy link
Contributor Author

@SlyngDK can we release this since it is an important fix?

@SlyngDK
Copy link
Contributor

SlyngDK commented Oct 25, 2025

@IvanPuntev
I have looked into this and thinks, the default should be to use the default provided ObjectMapper.
And maybe create support for provide a custom ObjectMapper for logging.

@IvanPuntev
Copy link
Contributor Author

@SlyngDK How do you propose to add the support for a custom object mapper? Currently the extension hardcodes the jackson factory in its processor at build time - https://github.com/quarkiverse/quarkus-logging-json/blob/main/deployment/src/main/java/io/quarkiverse/loggingjson/deployment/LoggingJsonProcessor.java#L53
There are no CDI injection, config or runtime hook.

@iqnev
Copy link

iqnev commented Nov 18, 2025

Hi @IvanPuntev do you know when the above changes will be merged?

@IvanPuntev
Copy link
Contributor Author

Hi @IvanPuntev do you know when the above changes will be merged?

I'm preparing a better solution and will commit it soon. After review it will be merged.

@IvanPuntev
Copy link
Contributor Author

The new changes are here - #395

@IvanPuntev IvanPuntev marked this pull request as draft November 20, 2025 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The objectMapper.findAndRegisterModules() not registering modules in quarkus-logging-json in native mode

3 participants