Redis-plugin - unresolved dependency: org.sedis#sedis_2.11;1.2.2: not found

[lnitram]

I tried to run the redis-plugin following this howto:

https://github.com/typesafehub/play-plugins/tree/master/redis#how-to-install

What I did:

• added to build.sbt: libraryDependencies += "com.typesafe.play.plugins" %% "play-plugins-redis" % "2.3.1"
• created play.plugins in app/conf
• added 550:com.typesafe.plugin.RedisPlugin to play.plugins
• ./activator
• compile
• run

[info] Resolving org.sedis#sedis_2.11;1.2.2 ...
[warn]  module not found: org.sedis#sedis_2.11;1.2.2
[warn] ==== local: tried
[warn] ==== activator-local: tried
[warn] ==== public: tried
[warn]   http://repo1.maven.org/maven2/org/sedis/sedis_2.11/1.2.2/sedis_2.11-1.2.2.pom
[warn] ==== typesafe-releases: tried
[warn]   http://repo.typesafe.com/typesafe/releases/org/sedis/sedis_2.11/1.2.2/sedis_2.11-1.2.2.pom
[warn] ==== typesafe-ivy-releasez: tried
[warn]   http://repo.typesafe.com/typesafe/ivy-releases/org.sedis/sedis_2.11/1.2.2/ivys/ivy.xml
[warn] ==== Typesafe Releases Repository: tried
[warn]   http://repo.typesafe.com/typesafe/releases/org/sedis/sedis_2.11/1.2.2/sedis_2.11-1.2.2.pom
[warn] ==== Typesafe Releases: tried
[warn]   http://repo.typesafe.com/typesafe/releases/org/sedis/sedis_2.11/1.2.2/sedis_2.11-1.2.2.pom
[...]
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: org.sedis#sedis_2.11;1.2.2: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[trace] Stack trace suppressed: run last *:update for the full output.
[error] (*:update) sbt.ResolveException: unresolved dependency: org.sedis#sedis_2.11;1.2.2: not found
[error] Total time: 316 s, completed 22.11.2014 22:18:00

[njovy]

I am having this issue on a new vm. Any updates on this?

[afrad]

Add "google-sedis-fix" at "http://pk11-scratch.googlecode.com/svn/trunk" to resolvers
See the comment of Denise https://groups.google.com/forum/#!topic/play-framework/j7-iaAb1_yM

[nhooey]

The http://pk11-scratch.googlecode.com/svn/trunk link is now an HTTP 404.

[htxiong]

@nhooey +1, we just start to get this error again today and the link is not available. we need to find an new solution.

[jroper]

@pk11 Do you know what's happened to sedis?

[graingert]

ok I'm uploading this to bintray now

[graingert]

You can now download at https://jcenter.bintray.com/org/sedis/

[graingert]

Simply add Resolver.jcenterRepo I've submitted a request to be included in Maven Central

It's now in Maven Central, you don't need to do anything and will "just work tm"

[urstoryent]

resolvers += "sedis-fix" at "https://dl.bintray.com/graingert/maven/"

[pk11]

@urstoryent thanks for taking care of this

[tremmert]

thanks for that, but I have the same problem with sedis_2.10;1.2.2. @graingert could you upload a 2.10;1.2.2 version please ?

[graingert]

Ok but you should totally upgrade your scala
On 14 May 2016 17:15, "Thomas Remmert" [email protected] wrote:

thanks for that, but I have the same problem with sedis_2.10;1.2.2.
@graingert https://github.com/graingert could you upload a 2.10;1.2.2
version please ?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#141 (comment)

[tremmert]

@graingert thank you so much !!!..

I know I should upgrade but I got a nasty set of dependencies, mainly around heavily using a version of slick that doesn't work with 2.11. But this did give me a warning and the motivation to do that very soon

By you uplodading the 2.10;1.2.2 version of sedis I got a few days to address this :-)

[graingert]

@tremmert done

[graingert]

@tremmert @urstoryent @lnitram
It's now published to Sonatype and will be on Maven Central within the hour is now in Maven Central. You don't need to do anything and sedis will "just work"

[graingert]

@gmethvin can you close this issue

[mienaikoe]

This is still an issue for 2.4.1 and 2.5.0
If there are no plans to add these versions to maven or ivy anytime soon, there should at least be a disclaimer on https://github.com/playframework/play-plugins/blob/master/redis/README.md