I'm seeing a problem where, although I reference the latest version of the following dependency, it still reports that I am able to update it. Specifically, I have this in my build:
Below is a session where (if I understand how things are supposed to work) it tells me that I have no dependencies on version 2.1.2 (as I would expect). So why does it suggest that I'm able to upgrade, when, AFAIKT, I have no transitive dependencies on the earlier version?
Thanks in advance, and let me know if you need other info.
Regards,
Phil
sbt:ue> dependencyUpdates
[info] Found 1 dependency update for ue
[info] org.scalameta:semanticdb-scalac:plugin->default(compile) : 2.1.2 -> 2.1.3
[info] Found 1 dependency update for vastblue
[info] org.scalameta:semanticdb-scalac:plugin->default(compile) : 2.1.2 -> 2.1.3
[info] Found 1 dependency update for apps
[info] org.scalameta:semanticdb-scalac:plugin->default(compile) : 2.1.2 -> 2.1.3
[success] Total time: 8 s, completed Dec 9, 2017 10:26:24 PM
sbt:ue> ;reload ;whatDependsOn org.scalameta semanticdb-scalac_2.12 2.1.2
[info] Loading settings from plugins.sbt ...
[info] Loading global plugins from /home/philwalk/.sbt/1.0/plugins/project
[info] Loading global plugins from /home/philwalk/.sbt/1.0/plugins
[info] Loading project definition from /opt/ue/project/project
[info] Loading settings from build.sbt,buildinfo.sbt,play-fork-run.sbt,plugins.sbt,sbt-ui.sbt ...
[info] Loading project definition from /opt/ue/project
[info] Loading settings from build.sbt ...
[info] Set current project to ue (in build file:/opt/ue/)
[info] Updating {file:/opt/ue/}vastblue...
[info] Done updating.
[success] Total time: 17 s, completed Dec 9, 2017 10:26:51 PM
A bit of additional info that might be irrelevant, here are some eviction warnings for subprojects "vastblue" and "apps" that reference "org.scalameta":
[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn] * com.lihaoyi:fastparse_2.12:1.0.0 is selected over {0.4.4, 0.4.3}
[warn] +- com.lihaoyi:scalaparse_2.12:1.0.0 (depends on 1.0.0)
[warn] +- vastblue:vastblue_2.12:0.1-SNAPSHOT (depends on 1.0.0)
[warn] +- org.scalameta:tokenizers_2.12:2.1.3 (depends on 0.4.4)
[info] * com.lihaoyi:sourcecode_2.12:0.1.4 is selected over 0.1.3
[info] +- com.lihaoyi:fastparse-utils_2.12:1.0.0 (depends on 0.1.4)
[info] +- com.lihaoyi:scalaparse_2.12:1.0.0 (depends on 0.1.4)
[info] +- com.lihaoyi:fastparse_2.12:1.0.0 (depends on 0.1.4)
[info] +- org.scalameta:common_2.12:2.1.3 (depends on 0.1.3)
[warn] * com.lihaoyi:fastparse_2.12:1.0.0 is selected over {0.4.4, 0.4.3}
[warn] +- apps:apps_2.12:0.1-SNAPSHOT (depends on 1.0.0)
[warn] +- com.lihaoyi:scalaparse_2.12:1.0.0 (depends on 1.0.0)
[warn] +- vastblue:vastblue_2.12:0.1-SNAPSHOT (depends on 1.0.0)
[warn] +- org.scalameta:tokenizers_2.12:2.1.3 (depends on 0.4.4)
[warn] +- com.trueaccord.scalapb:scalapb-runtime_2.12:0.6.2 (depends on 0.4.4)
[info] Here are other depedency conflicts that were resolved:
[info] * com.lihaoyi:sourcecode_2.12:0.1.4 is selected over 0.1.3
[info] +- com.lihaoyi:fastparse-utils_2.12:1.0.0 (depends on 0.1.4)
[info] +- com.lihaoyi:scalaparse_2.12:1.0.0 (depends on 0.1.4)
[info] +- com.lihaoyi:fastparse_2.12:1.0.0 (depends on 0.1.4)
[info] +- org.scalameta:common_2.12:2.1.3 (depends on 0.1.3)
I love this plugin, BTW!
I'm seeing a problem where, although I reference the latest version of the following dependency, it still reports that I am able to update it. Specifically, I have this in my build:
libraryDependencies += "org.scalameta" %% "scalameta" % "2.1.3"
Below is a session where (if I understand how things are supposed to work) it tells me that I have no dependencies on version 2.1.2 (as I would expect). So why does it suggest that I'm able to upgrade, when, AFAIKT, I have no transitive dependencies on the earlier version?
Thanks in advance, and let me know if you need other info. Regards, Phil
A bit of additional info that might be irrelevant, here are some eviction warnings for subprojects "vastblue" and "apps" that reference "org.scalameta":