-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The objectMapper.findAndRegisterModules() not registering modules in quarkus-logging-json in native mode #305
Comments
The issue is so capsulated that I used some reflection magic to fix this: |
For all that comes to this ticket here are the files that I wrote to fix this: quarkus-logging-json-workaround-36937.zip And the code itself for indexing from google/github:
|
The other part of the code:
|
And the last one, know that all are in the zip attached above.
|
Describe the bug
If the JavaTimeModule class is available, I expect the ObjectMapper used by quarkus-logging-json to register it as a module.
That does not happen in native build.
Expected behavior
If the JavaTimeModule class is available, I expect the ObjectMapper used by quarkus-logging-json to register it as a module.
Actual behavior
This exception is thrown:
How to Reproduce?
A simple code to test:
That will not dump any json message and will log an error that jsr310 should be registered.
Output of
uname -a
orver
5.15.0-86-generic #96-Ubuntu SMP Wed Sep 20 08:23:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk 17.0.8.1 2023-08-24
Mandrel or GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.2.6.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: