Please enable JavaScript.

Coggle requires JavaScript to display documents.

Gradle Talk - Coggle Diagram

- - - - dealing with incompatible versions of a runtime (e.g: Scala 2.11 vs Scala 2.12)
      - misaligned dependencies of a component (e.g: Jackson Databind 2.9.0 with Jackson Core 2.9.4)
      - builds suddenly failing because of a dynamic version upgrade (version “1.+”)
      - rejecting vulnerable transitive dependencies
      - removing unused dependencies
      - inconsistent versions between subprojects in the same repository
      - multiple libraries providing the same feature (a single logger API, but you end up with multiple implementations)
      - 2 components depending on the same module but with different, incompatible, APIs
  - - - Conflict between versions. Lib A wants higher versions than lib B.
    - - The Gradle Module Metadata answer
      - Adding the missing bits to existing Jackson metadata
        Allows to enrich published pom metadata with the missing information when it is processed by Gradle
- - - - major version upgrades (breaks binary compatibility)
      - vulnerabilities (you should really not include 1.6 because it has a CVE)
      - regressions (there’s a bug in 1.6)
      - library belongs to a larger set of modules which need to share the same version (e.g Jackson Core, Databind, Annotations, …)