-
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
Mocking Rest client does not work with 2.14.0.CR1 #29128
Comments
/cc @Sgitario, @cescoffier, @geoand |
@mkouba @Ladicek this seems to be an Arc issue. Essentially with Quarkus I assume this is due to 7c77aa6 |
That commit can safely be reverted with Jandex 3.0.1, but I would be surprised if that's what causes the issue. I'll take a look tomorrow if noone beats me to it. |
The commit was just my best guess, I could certainly be off the mark |
Yeah, that looks like a side effect of this issue. So |
We'll need to address this because this manual mocking won't work otherwise |
I agree, I am just not sure how to do that yet :) |
Let's figure it out tomorrow 😜 |
I am not sure I understand this, can you elaborate please? |
That is just a poorly formulated remnant of my brain trying to figure out how this works behind the scenes; feel free to disregard that :) I discussed this with @mkouba and @Ladicek and while we haven't discovered any silver bullets, we could improve it by adding interfaces into bean types. It is a little but of extra processing but solves the issue presented here. |
Describe the bug
Mocking a Client like this worked with 2.13.3
but does not with 2.14
Expected behavior
Mocking works.
Actual behavior
The mock is ignored.
How to Reproduce?
code-with-quarkus-client-mock.zip
There is a simple test included.
If you switch to 2.13.3 the test passes.
Output of
uname -a
orver
windows/ubuntu
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.14.0.CR1
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: