New sbt "function" configuration not found in X / unresolved (transitive) dependencies
And a recent new "feature" in sbt, perhaps 0.13.7 or 0.13.8, is very annoying behavior when transitive dependencies are no longer encountered.
For example. I have a project A that depends on library B version 1.25.1, which depends on library C version 1.13.1. Naturally, only bibliographic dependency B is defined in A, because I don't want to define an entire tree from dozens of sub-libraries. Ok, this is building.
I am now updating the dependency in A to become library B version 1.25.2, which in turn depends on library C version 1.13.2. Now sbt is complaining about a rather useless configuration not found in library-C; 1.13.2: "master". Required from Library-B; 1.25.2 compile " and then throw out the" unresolved dependency . " Sbt didn't even bother to download the 1.13.2 C library from Maven Central or actually find it already published locally. The only way to" solve "this is to add the C library dependency version 1.13.2 to project A, which I don't want to do.
Here is an example printout:
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: de.sciss#scalacolliderugens-core_2.11;1.13.2: configuration not found in de.sciss#scalacolliderugens-core_2.11;1.13.2: 'master'. It was required from de.sciss#scalacolliderswing-core_2.11;1.25.2 compile
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Unresolved dependencies path:
[warn] de.sciss:scalacolliderugens-core_2.11:1.13.2
[warn] +- de.sciss:scalacolliderugens-plugins_2.11:1.13.2
[warn] +- de.sciss:scalacolliderswing-core_2.11:1.25.2 (/home/hhrutz/Documents/devel/SoundProcesses/build.sbt#L167)
[warn] +- de.sciss:soundprocesses-compiler_2.11:2.20.0-SNAPSHOT
I'm guessing this is an annoying bug in sbt, or is there any deeper arguments for dropping transitive dependencies that I don't understand?
source to share