Release 11.9 introduces binary incompatibility (NoSuchMethodError)

[metteo]

Refactoring of some methods from Feign.Builder into BaseBuilder caused some incompatibilities on bytecode level. I guess there is no way to fix this now, but I suggest plugging in some tool that automatically detects such problems during CI: https://lvc.github.io/japi-compliance-checker/

EDIT: Moved the method from the title for better indexing: Feign.Builder.contract(Contract)

[velo]

How can that happen?!

[metteo]

Will try to prepare a mini test project after work today. Long story short, project compiled with version 1.19 but run with 1.18 on classpath (without recompiling) will throw the Exception.

Edit: 🤔

[pstorch]

Maybe related, we got this NoSuchMethodError with Feign 1.19:

Caused by: java.lang.NoSuchMethodError: 'feign.Feign$Builder feign.Feign$Builder.options(feign.Request$Options)'

[velo]

Will try to prepare a mini test project after work today. Long story short, project compiled with version 1.19 but run with 1.18 on classpath (without recompiling) will throw the Exception.

Why compile with .19 and run with .18?

I would understand the other way around...

[freddidierRTE]

I have same problem with another method :

java.lang.NoSuchMethodError: 'feign.Feign$Builder feign.Feign$Builder.decoder(feign.codec.Decoder)

[velo]

@freddidierRTE By any chance you mixing feign versions too?

[metteo]

We have library which was updated by renovate to 11.9 After upgrading that library in an application which has maven dependency management set to 11.8 the project would not run. Only after upgrading Feign in the app at the same time as the library, it worked.

[freddidierRTE]

@freddidierRTE By any chance you mixing feign versions too?

You are right , i realized i m using openfeign 11.9 for my application but spring-cloud-starter-openfeign for my test code which is still on openfeign 11.8

Thanks !

[velo]

Do you guys think this help/solves this problem?
https://github.com/OpenFeign/feign#mavens-bill-of-material-bom

[pstorch]

For us it's solved. We found another lib which referenced the 11.8. After upgrading that one our project build again.

[erwinw]

This is causing some major headaches for us; any chance this can be addressed in a follow-up version?