-
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
[2.13] Sanitize the behavior of provided ExceptionMapper classes in dev-mode #32619
Conversation
User provided ExceptionMapper classes now takes precedence over the Quarkus provided NotFoundExceptionMapper. This is done in a way that does not change anything but this specific behavior, everything else concerning exception handling continues to work as before. Note also that this does not change the spec compliance in any way Fixes: quarkusio#7883
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
This comment has been minimized.
This comment has been minimized.
Failing Jobs - Building 9682199
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
⚙️ JVM Tests - JDK 11 #- Failing: integration-tests/logging-gelf
📦 integration-tests/logging-gelf✖
|
Right, done. |
Thanks @gsmet |
javax
/jakarta
package name changes, the backporting may not be done automatically)