NET-A-PORTER/scala-uri

unresolved scala-sbt dependency

Closed this issue · 5 comments

almoehi commented

when I add scala-uri to my build.sbt I get this:

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: org.scala-sbt#sbt;0.13.0-RC2: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

I added this dep to my build.sbt:
"com.netaporter" % "scala-uri" % "0.4.0",

I guess we have to bump the sbt version?

almoehi commented

excluding transitive dependency and also switching to SNAPSHOT version worked for me:

"com.netaporter" %% "scala-uri" % "0.4.1-SNAPSHOT" excludeAll(ExclusionRule(organization = "org.scala-sbt")),

rvangsgaard commented

I am still seeing an error in a Play 2.2.1 project with this resolver and the SNAPSHOT version

resolvers += "Sonatype OSS" at "http://oss.sonatype.org/content/public",

"com.netaporter" %% "scala-uri" % "0.4.1-SNAPSHOT" excludeAll(ExclusionRule(organization = "org.scala-sbt")),

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: com.netaporter#scala-uri_2.10;0.4.1-SNAPSHOT: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[trace] Stack trace suppressed: run last *:update for the full output.
[error] (*:update) sbt.ResolveException: unresolved dependency: com.netaporter#scala-uri_2.10;0.4.1-SNAPSHOT: not found
[error] Total time: 6 s, completed Jan 24, 2014 4:02:44 PM
theon commented

Hi,

I think the SNAPSHOT repo in the README was wrong. Fixed it now. Could you try this one:

resolvers += "Sonatype OSS" at "http://oss.sonatype.org/content/repositories/snapshots"
rvangsgaard commented

Thank you. I had to move on and choose spray-http instead, which lives up to my needs - if you have any comments on this choice, please let me know.

theon commented

spray-http is great. scala-uri has api support for some esoteric things like matrix parameters, but if you don't need those things I'd say that spray-http is probably a better choice as spray has bigger community behind it.