-
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
Make RESTEasy Reactive path matching more spec compliant #26101
Conversation
This comment has been minimized.
This comment has been minimized.
RESTEasy Classic already behaves properly, so we should follow this patterns Fixes: quarkusio#26016
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.
It looks good to me. Though this change should be listed in the release notes.
Definitely. That's why I added the |
@gsmet how do you feel about getting this into |
Failing Jobs - Building 36e95a0
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 #📦 integration-tests/gradle✖
|
Tests fails as path called by Rest Client is not found. IMHO that's due to [this PR](quarkusio/quarkus#26101). One way or another, adjusting resource/client paths fixes the issue.
Tests fails as path called by Rest Client is not found. IMHO that's due to [this PR](quarkusio/quarkus#26101). One way or another, adjusting resource/client paths fixes the issue. refactor
Tests fails as path called by Rest Client is not found. IMHO that's due to [this PR](quarkusio/quarkus#26101). One way or another, adjusting resource/client paths fixes the issue.
Tests fails as path called by Rest Client is not found. IMHO that's due to [this PR](quarkusio/quarkus#26101). One way or another, adjusting resource/client paths fixes the issue.
Tests fails as path called by Rest Client is not found. IMHO that's due to [this PR](quarkusio/quarkus#26101). One way or another, adjusting resource/client paths fixes the issue.
RESTEasy Classic already behaves properly, so we should follow this patterns
Fixes: #26016