Geek Answers Handbook

Unresolved SBT dependency org.scala-sbt # sbt_2.9.1; 0.12.1: not found, playback examples

I am trying to run samples in a Play 2.0 environment, but when I go to run "play" or "sbt".

When I go to the directory "/ samples / scala / helloworld", I run "sbt" and I get:

[info] Loading project definition from C:\src\Play20\samples\scala\helloworld\project [warn] module not found: play#sbt-plugin;2.0 [warn] ==== typesafe-ivy-releases: tried [warn] http://repo.typesafe.com/typesafe/ivy-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0/ivys/ivy.xml [warn] ==== sbt-plugin-releases: tried [warn] http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0/ivys/ivy.xml [warn] ==== local: tried [warn] C:\Users\labra\.ivy2\local\play\sbt-plugin\scala_2.9.2\sbt_0.12\2.0\ivys\ivy.xml [warn] ==== Typesafe repository: tried [warn] http://repo.typesafe.com/typesafe/releases/play/sbt-plugin_2.9.2_0.12/2.0/sbt-plugin-2.0.pom [warn] ==== public: tried [warn] http://repo1.maven.org/maven2/play/sbt-plugin_2.9.2_0.12/2.0/sbt-plugin-2.0.pom [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: play#sbt-plugin;2.0: not found [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] [warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes. [warn] play:sbt-plugin:2.0 (sbtVersion=0.12, scalaVersion=2.9.2) [warn] sbt.ResolveException: unresolved dependency: play#sbt-plugin;2.0: not found at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:214) . . . at java.lang.Thread.run(Thread.java:722) [error] (*:update) sbt.ResolveException: unresolved dependency: play#sbt-plugin;2.0: not found Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? [info] Loading project definition from C:\src\Play20\samples\scala\helloworld\project [warn] module not found: play#sbt-plugin;2.0 [warn] ==== typesafe-ivy-releases: tried [warn] http://repo.typesafe.com/typesafe/ivy-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0/ivys/ivy.xml [warn] ==== sbt-plugin-releases: tried [warn] http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0/ivys/ivy.xml [warn] ==== local: tried [warn] C:\Users\labra\.ivy2\local\play\sbt-plugin\scala_2.9.2\sbt_0.12\2.0\ivys\ivy.xml [warn] ==== Typesafe repository: tried [warn] http://repo.typesafe.com/typesafe/releases/play/sbt-plugin_2.9.2_0.12/2.0/sbt-plugin-2.0.pom [warn] ==== public: tried [warn] http://repo1.maven.org/maven2/play/sbt-plugin_2.9.2_0.12/2.0/sbt-plugin-2.0.pom [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: play#sbt-plugin;2.0: not found [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] [warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes. [warn] play:sbt-plugin:2.0 (sbtVersion=0.12, scalaVersion=2.9.2) [warn] sbt.ResolveException: unresolved dependency: play#sbt-plugin;2.0: not found at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:214) at sbt.IvyActions$$anonfun$update$1.apply(IvyActions.scala:122) . . . at java.lang.Thread.run(Thread.java:722) [error] (*:update) sbt.ResolveException: unresolved dependency: play#sbt-plugin;2.0: not found Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? q

I installed sbt version 12.1 from http://www.scala-sbt.org/release/docs/Getting-Started/Setup

I noticed a similar question: https://groups.google.com/forum/?fromgroups=#!topic/simple-build-tool/DGUbWsgZiLw

The answers seem to be related to the SBT version of “Launcher”, how can I find out that this is my version of sunc for Launcher? And how can I update it?

I also tried to compile xsbt from the source code, but when I run "sbt build-all" I get:

  . . . [info] Reading library jar [C:\compi\jdk\jre\lib\rt.jar] [error] Error: Can't read [ proguard.ClassPathEntry@73abdb5e ] (Can't process class [com/oracle/net/Sdp$1.class] (Unsupported version number [51.0] for class format)) [error] java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded [error] Use 'last' for the full log.

However, my problem is not in compiling xsbt, but in how I can execute "Playback Examples"

When I run "sbt sbt-version" in a new folder, I get:

 [info] Set current project to default-85f41b (...) [info] 0.12.1
+7
source share
5 answers

If you look at project / plugins.sbt , you will see that it expects the system property play.version be set:

 addSbtPlugin("play" % "sbt-plugin" % Option(System.getProperty("play.version")).getOrElse("2.0"))

So you must either provide the required play.version property

 $ sbt -Dplay.version=2.1-RC1

or just change plugins.sbt as

 addSbtPlugin("play" % "sbt-plugin" % "2.1-RC1")
+6
source

For Activator 1.0 users :

This issue may occur when you upgrade your Play project to a later version after . You upload the project to Activator 1.0. This is because Activator creates files in the / project directory that look like activator-...-shim.sbt . Delete these files, and Activator should solve the problem at the next compilation.

+4
source

I solved the problem after switching to Play 2.1-RC1

I also had a problem with some dependencies that I decided to insert:

 // The Typesafe snapshots repository resolvers += "Typesafe Snapshots" at "http://repo.typesafe.com/typesafe/snapshots/"

in plugins.sbt

I just followed: https://github.com/playframework/Play20/wiki/Repositories

+2
source

For play 2.0.2, version 2.0.2 SBT worked great in my project. I changed the addSbtPlugin line in the plugins.sbt file to:

 addSbtPlugin("play" % "sbt-plugin" % "2.0.2")

It should be similar for earlier versions. As Labra already noted, since this version of SBT is not the latest, you probably need to add the following recognizer to get it:

 resolvers += "Typesafe Snapshots" at "http://repo.typesafe.com/typesafe/snapshots/"

Another way to get rid of this problem is to update the Play Framework for your project to the latest version, if possible. This is probably the best choice in the long run, as it allows you to maintain your current code base.

+1
source

Following Jose's answer, I did this, but with this resolver:

 "Typesafe Snapshots" at "http://repo.typesafe.com/typesafe/maven-releases"
0
source

More articles:


All Articles