-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Erroneous warning 'Detected use of JSON but no extension added' when using Jax-rs MessageBodyReader #28195
Labels
Milestone
Comments
/cc @FroMage, @geoand, @stuartwdouglas |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 27, 2022
geoand
added a commit
that referenced
this issue
Sep 28, 2022
Take application provided JSON providers when warning about missing JSON feature
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 3, 2022
…SON feature Fixes: quarkusio#28195 (cherry picked from commit 2e21ad0)
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is a warning printed that no json extension is added, but I am using a MessageBodyReader/Writer which makes the warning erroneous.
Expected behavior
No warning should be printed
Actual behavior
How to Reproduce?
From a Quarkus Jaxrs project, add your own serde:
Output of
uname -a
orver
Darwin 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:17:10 PDT 2022; root:xnu-8020.140.49~2/RELEASE_X86_64 x86_64
Output of
java -version
openjdk 11.0.13
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.12.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.8.6
Additional information
No response
The text was updated successfully, but these errors were encountered: