gradle-consistent-versions icon indicating copy to clipboard operation
gradle-consistent-versions copied to clipboard
verified publisher icon palantir

Upgrading through different major versions

Open iamdanfox opened this issue 6 years ago • 0 comments

What happened?

In a project's transitive dependency graph, something depended on 1.X of [Redacted] but another project had 2.X.

GCV happily picked the highest 2.X release, but this resulted in broken behaviour at runtime.

What did you want to happen?

Something to help save devs time and catch this before runtime, possible ideas:

  • ~Just fail if major versions conflict~ (not feasible because guava 23 and 24 are pretty much fine)
  • require people to acknowledge major version incompatibilities? (maybe in the lockfile)
  • recommend using some static analysis like missinglink?
  • clear documentation warning people this is an unsolved problem?

iamdanfox avatar Mar 07 '19 19:03 iamdanfox