Skip to content

Version ranges (dynamic revision) have issues with bintray #2005

@jroper

Description

@jroper

steps

build.sbt:

lazy val root = (project in file(".")).
  settings(
    libraryDependencies += "org.webjars" %% "webjars-play" % "2.1.0-3",
    resolvers += Resolver.typesafeRepo("releases")
  )

problem

root> update
[info] Updating {file:/Users/eugene/work/quick-test/sbt-2005/}root...
[info] Resolving play#play_2.10;[2.1.0,2.1.2] ...
[warn]  module not found: play#play_2.10;[2.1.0,2.1.2]
[warn] ==== local: tried
[warn]   /Users/eugene/.ivy2/local/play/play_2.10/[revision]/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/play/play_2.10/[revision]/play_2.10-[revision].pom
[warn] ==== typesafe-releases: tried
[warn]   https://repo.typesafe.com/typesafe/releases/play/play_2.10/[revision]/play_2.10-[revision].pom
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: play#play_2.10;[2.1.0,2.1.2]: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn] 
[warn]  Note: Unresolved dependencies path:
[warn]      play:play_2.10:[2.1.0,2.1.2]
[warn]        +- org.webjars:webjars-play_2.10:2.1.0-3 (<set>#L1-1)
[warn]        +- root:root_2.10:0.1-SNAPSHOT
[trace] Stack trace suppressed: run last *:update for the full output.
[error] (*:update) sbt.ResolveException: unresolved dependency: play#play_2.10;[2.1.0,2.1.2]: not found
[error] Total time: 10 s, completed Jun 24, 2015 5:43:57 PM

original report

See https://groups.google.com/d/msg/play-framework/ES8WDB0pIA0/Q8bYH9jaRZoJ

And comment from @jsuereth:

Version ranges are generally a really bad idea in Ivy. I need to check implementation, but I think it tries to do a directory listing using nonstandard techniques.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions