-
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
Move all RESTEasy Reactive configuration under 'quarkus.resteasy-reactive' #16310
Conversation
…tive' For the time being, the old 'quarkus.rest' config root is still supported, but that support will be removed once the 'vertx-4' branch has been merged into main (at which point the TCK will be updated to use the new values). However the old 'quarkus.security.jaxrs.deny-unannotated-endpoints' is not supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's wait for the merge of 2.0 before merging that, please.
Sure yeah |
Failing Jobs
|
^ doesn't look like it corresponds to what actually happened @gsmet @gastaldi |
For good measure, I'll rebase this PR onto main |
@geoand yeah for the bot, it's because I cancelled the build to prioritize the 1.13.1 backport PR. I should probably handle this at the bot level. |
@gsmet Gotcha. I was going to rebase the PR, but since you merged it, no need :) |
For the time being, the old
quarkus.rest
config root is still supported,but that support will be removed once the
vertx-4
branch has been mergedinto main (at which point the TCK will be updated to use the new values).
However the old
quarkus.security.jaxrs.deny-unannotated-endpoints
is notsupported