-
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
Fix build issue when client and server RESTEasy Reactive jackson deps are used together #16368
Fix build issue when client and server RESTEasy Reactive jackson deps are used together #16368
Conversation
… are used together
@famod is there a way we have can have an enforcer rule that enforces that all classes that extend |
ArchUnit would be way more suitable for such things. |
But I don't see I way that such rules could apply to all modules, no? |
It's not totally trivial, but via surefire you can run tests from jars so you could define those rules in a central module and add executions to all modules that need to be checked (ideally only add it to a parent to cover as much as possible). |
Understood, thanks 👍 |
@geoand are you planning to do that? I think ArchUnit would be a valuable addition to the Quarkus QA. |
I don't have any immediate plans, no. But it's certainly something I'll keep in mind if no one else comes up with something in the meantime |
thanks @geoand ! |
YW! |
After quarkusio#27203, we can customize the object mappers to be used by REST Client Reactive. However, because of quarkusio#16368, the implementation was never picked up when the resteasy reactive jackson extension is in place. I tried to remove the ResteasyReactiveJacksonProviderDefinedBuildItem build item and surprisingly everything kept working fine (I verified the test that was added as part of quarkusio#16368. Fix quarkusio#23979
After quarkusio#27203, we can customize the object mappers to be used by REST Client Reactive. However, because of quarkusio#16368, the implementation was never picked up when the resteasy reactive jackson extension is in place. I tried to remove the ResteasyReactiveJacksonProviderDefinedBuildItem build item and surprisingly everything kept working fine (I verified the test that was added as part of quarkusio#16368. Fix quarkusio#23979
After quarkusio#27203, we can customize the object mappers to be used by REST Client Reactive. However, because of quarkusio#16368, the implementation was never picked up when the resteasy reactive jackson extension is in place. I tried to remove the ResteasyReactiveJacksonProviderDefinedBuildItem build item and surprisingly everything kept working fine (I verified the test that was added as part of quarkusio#16368. Fix quarkusio#23979
After quarkusio#27203, we can customize the object mappers to be used by REST Client Reactive. However, because of quarkusio#16368, the implementation was never picked up when the resteasy reactive jackson extension is in place. I tried to remove the ResteasyReactiveJacksonProviderDefinedBuildItem build item and surprisingly everything kept working fine (I verified the test that was added as part of quarkusio#16368. Fix quarkusio#23979
The issue was originally reported here.