“NoSuchMethodErrors” due to multiple versions of com.google.protobuf:protobuf-java:jar

[saturnism]

“NoSuchMethodErrors” due to multiple versions of com.google.protobuf:protobuf-java:jar

[Bing-ok]

@saturnism Thanks for your support! I have seen the changes. By the way, if you didn't remove the dependency on spring cloud gcp, which one of the solutions I proposed above would you choose?

[Bing-ok]

Could you help me review this issue? 👍 Thanks! @saturnism

[saturnism]

hi @Bing-ok ! apologies for the late reply. is this in your project, or my sample here? could i trouble you to provide some instructions to reproduce this? thanks!

[Bing-ok]

Hi @saturnism ! I found this issue in your example by analyzing depedencies and code. I had given details of invocation paths.

[saturnism]

@Bing-ok i see the issue! Thanks for the dep tree. I think we can remove the dependency on spring cloud gcp since we aren't using this at all.

[saturnism]

i pushed the changes, pls take a look! thanks!

[saturnism]

@Bing-ok if the highest version works, I would:

1. Use Maven enforcer's requireUpperBound rule to make sure it's using the higher of the version
2. Import Protobuf BOM in the dependencyManagement section to specify the Protobuf version, but also ensure all protobuf modules are aligned to the same version

So it's close to your first suggestion, but rather than dependency manage a single protobuf artifact, import the BOM to make sure all protobuf modules are also updated to the version you want to use.

I have a summary of some of the strategies here: https://saturnism.me/talk/surviving-dependency-hell-maven/ . Specifically the reason I'd import the BOM is to avoid version misalignment issues.