4 ms·

I have not experienced this running guava 16-23 in various apps. Maybe incompatible but they're good about security patches for old versions. I have never seen

• BeeOnRope 7y ago
  It's very easy to get a Guava version conflict because (a) Guava frequently adds new stuff, and (b) Guava semi-frequently deprecates and removes stuff a couple versions later. So all you need is one dep that needs Guava version X with method M that is removed in version X+2 (say) and another dep that needs something new introduced in version X+2, and you have a Guava version conflict. That's, Guava releases are not backwards compatible due to removal of classes and methods. You can sometimes fix this with a technology like shade or OSGi or whatever to allow private copies but it does not always work.
• aphexairlines 7y ago
  Transitive dependencies on Guava 19, 20, 21 can lead to runtime crashes if your dependencies differ in what guava versions they expected when they were compiled: https://www.google.com/search?q=guava+nosuchmethoderror https://www.google.com/search?q=guava+nosuchmethoderror