Skip to content
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

Add support for Feign 12.5+ #2127

Open
wants to merge 1 commit into
base: 1.7
Choose a base branch
from

Conversation

nilo85
Copy link
Contributor

@nilo85 nilo85 commented Mar 5, 2024

Feign 12.5 made the builder.build() method final, and started internally clone it...

This breaks resilience4j integration with feign and renders resilience4j completely unused by feign.

In version 10.9 they introduced an api to add "capabilities" to the feign client.

Here I have made changed to the 1.7 branch (the release I need) that implements this new pattern instead, and provides a fallback using old pattern for backwards compatibility down to 10.9.

Merging this means minimum version of feign to use would be 10.9. and works with latest

@nilo85
Copy link
Contributor Author

nilo85 commented Mar 5, 2024

This is applied to the 1.7 branch, as I need this fixed in 1.7, if this is approved and we create a new 1.7.x release I am happy to port these changes to 2.0 branch =)

Feign 12.5 made the builder.build() method final, and started internally clone it...

This breaks resilience4j integration with feign and renders resilience4j completely unused by feign.

In version 10.9 they introduced an api to add "capabilities" to the feign client.

Here I have made changed to the 1.7 branch (the release I need) that implements this new pattern instead, and provides a fallback using old pattern for backwards compatibility down to 10.9.

Merging this means minimum version of feign to use would be 10.9. and works with latest
@mateusz-bajorek
Copy link

Yes, porting this to 2.x would be appreciated as well :)

@nilo85
Copy link
Contributor Author

nilo85 commented Mar 6, 2024

follow up for 2.0 branch #2129 (simple cherry-pick seems to be enough)

@nilo85
Copy link
Contributor Author

nilo85 commented Mar 6, 2024

follow up for master branch #2130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants