keroncap.blogg.se - Gradle versions

It also depends on some other library which itself depends on Firebase Analytics but 18.0.3 version. Version ConflictĬan happen when two components depend on the same module but on different versions.įor instance: Our project depends on Firebase Analytics - “:firebase-analytics:17.5.0”.

Implementation conflict - when the dependency graph contains a module that provides the same implementation.įor this blog, we are going to explore version conflict resolution.

Version conflict - when two or more dependencies require a given dependency but with different versions.

While doing the dependency resolution Gradle can handle two types of conflicts:

When a specific dependency, that is a module with a version, is identified as part of the graph, retrieve its metadata so that its dependencies can be added in turn.ĭuring those phases, Gradle may encounter conflicts and can resolve them automatically.

When a new dependency is added to the graph, perform conflict resolution to determine which version should be added to the graph.

Gradle dependency resolution and conflict typesĪccording to the Gradle documentation dependency resolution is a process that consists of two phases, which are repeated until the dependency graph is complete:

Bonus: StrictVersionMatcher Gradle plugin.Resolving accidental upgrades - ResolutionStrategy.Accidental dependency upgrades, handling multiple versions.Gradle dependency resolution and conflict types.