Open kryptt opened 9 years ago
It is possible to use ivy dependency ranges in sbt. But when doing so, this plugin fails to validate latest versions against a project's specified ranges:
> dependencyUpdates [info] Found 12 dependency updates for msw-backend [info] ch.qos.logback:logback-classic : [1.1,2.0[ -> 1.1.3 [info] com.beachape:enumeratum : [1.1,2.0[ -> 1.3.0 [info] com.github.alexarchambault:argonaut-shapeless_6.1 : [0.3,0.4[ -> 0.3.1 [info] com.github.cb372:scalacache-guava : [0.5,1.0[ -> 0.6.4 [info] me.lessis:courier : [0.1,1.0[ -> 0.1.3 [info] net.ceedubs:ficus : [1.1,2.0[ -> 1.1.2 [info] org.flywaydb:flyway-core : [3.2,4.0[ -> 3.2.1 [info] org.mindrot:jbcrypt : [0.2,1.0[ -> 0.3m [info] org.scoverage:scalac-scoverage-plugin_2.11:provided : 1.1.0 -> 1.1.1 [info] org.scoverage:scalac-scoverage-runtime_2.11:provided : 1.1.0 -> 1.1.1 [info] org.specs2:specs2-matcher-extra:test : [3.6,3.7[ -> 3.6.4 [info] org.specs2:specs2-scalacheck:test : [3.6,3.7[ -> 3.6.4 [success] Total time: 47 s, completed Aug 11, 2015 3:49:55 PM
Yes, it is a known problem similar to #9. Thanks for reporting.
It is possible to use ivy dependency ranges in sbt. But when doing so, this plugin fails to validate latest versions against a project's specified ranges: