Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ConflictManager.strict doesn't always report conflicts with cached resolution

See original GitHub issue

We’ve had reports that under some circumstances that ConflictManager.strict doesn’t always catch the conflicts.

steps

Build that contains conflicts.

lazy val finagleVersion = "6.43.0"
lazy val jacksonDatabindVersion = "2.8.8.1"

lazy val app = (project in file("app"))
  .settings(
    conflictManager in ThisBuild := ConflictManager.strict,
    scalaVersion in ThisBuild := "2.11.11",
    libraryDependencies ++= Seq(
      "com.twitter" %% "finagle-http" % finagleVersion,
      "com.twitter" %% "finagle-core" % finagleVersion,
      "com.fasterxml.jackson.core" % "jackson-databind" % jacksonDatabindVersion
    ),
    updateOptions := updateOptions.value.withCachedResolution(true)
  )

update

problem

update succeeds.

expectation

update should fail.

notes

sbt version: 0.13.15

Eviction warning is not empty if you run evicted.

[info] Here are other libraries that were evicted:
[info] 	* com.fasterxml.jackson.core:jackson-databind:2.8.4 -> 2.8.8.1 (caller: org.scala-sbt.temp:temp-resolve-be3a39ab4f9850722efd52421b83abae0a33293a:1.0)
[info] 	* com.fasterxml.jackson.core:jackson-annotations:2.8.0 -> 2.8.4 (caller: com.fasterxml.jackson.module:jackson-module-scala_2.11:2.8.4, com.fasterxml.jackson.core:jackson-databind:2.8.4)
[info] 	* com.fasterxml.jackson.core:jackson-core:2.8.4 -> 2.8.8 (caller: com.fasterxml.jackson.core:jackson-databind:2.8.8.1)
[info] 	* org.scala-lang:scala-library:2.11.8 -> 2.11.11 (caller: org.scala-sbt.temp:temp-resolve-a2327a4988b8b897776cc563c2b13a6b14568db5:1.0)

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

lianchengcommented, Aug 29, 2017

@eed3si9n You probably want to use a permlink instead: https://github.com/sbt/librarymanagement/blob/6fc7bc6dc9241ba1c668a61e5a80c87563d7b21f/ivy/src/main/scala/sbt/internal/librarymanagement/ivyint/CachedResolutionResolveEngine.scala#L700-L731

0reactions

elbakramercommented, Aug 10, 2018

Possible duplicate of #2246

Top Results From Across the Web

sbt/sbt - Gitter

Hello, why sbt (1.3.5) fail to resolve identical dependencies in strict mode? conflictManager := sbt.ConflictManager.strict libraryDependencies += "io.grpc" ...

semantics of dependency resolvers - eed3si9n

The problem is that strict conflict manager doesn't seem to prevent eviction. show externalDependencyClasspath happily returns com.typesafe: ...

How to fix Evicted Modules issue in Apache Ivy - Stack Overflow

this conflicts manager resolve conflicts by selecting all revisions. Also called the NoConflictManager, it doesn't evict any modules. I had to put the...

Better management of transitive dependencies and conflicts

Strict conflict manager. By default, both Ivy and coursier tolerate that the dependency graph contains two different versions of a library, in ...

Apache Ivy™ Documentation 2.5.1

Finally, the retrieve task copies the resolved jars from the Ivy cache to the ... This is due to the fact that we...