Unable to install new 0.11.3 sbt on Ubuntu 10.04LTS

Question

This process worked fine in 0.11.2, but the recent change of wrt to sbt group id changed to org.scala-sbt (from org.scala-tools.sbt) seems to break the dependency.

I have a 10.04 LTS machine to which I added the debupesafe repository using the deb deb file described in: https://github.com/harrah/xsbt/wiki/Getting-Started-Setup .

When I try to install from a repo, I get:

[warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3: not found [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] module not found: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3 [warn] ==== typesafe-ivy-releases: tried [warn] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/scripted-plugin_2.9.1/0.11.3/ivys/ivy.xml [warn] ==== local: tried [warn] /home/jasonmaclulich/.ivy2/local/org.scala-tools.sbt/scripted-plugin_2.9.1/0.11.3/ivys/ivy.xml [warn] ==== Typesafe Repo: tried [warn] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/scripted- plugin_2.9.1/0.11.3/ivys/ivy.xml [warn] ==== public: tried [warn] http://repo1.maven.org/maven2/org/scala-tools/sbt/scripted-plugin_2.9.1/0.11.3/scripted-plugin_2.9.1-0.11.3.pom 

How do I instruct sbt to look for a script plugin with the id of the right group?

I also tried manual installation with this launcher (following UNIX installation instructions):

//typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.11.3-2/sbt-launch.jar

And I still get the following unresolved dependency:

 [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :::::::::::::::::::::::::::::::::::::::::::::: [warn] :: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3: not found [warn] :::::::::::::::::::::::::::::::::::::::::::::: 

Thoughts?

Thanks, Jason.

Answer 1

I thought I was updating this with the way I circumvented it if I explicitly installed the sbt version in 0.11.2 in the project / build.properties file, i.e. sbt.version=0.11.2 .

 Detected sbt version 0.11.2 Cannot find sbt launcher 0.11.2 Please download: From http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.2/sbt-launch.jar To /home/<username>/.sbt/.lib/0.11.2/sbt-launch.jar 

Then I installed the necessary files, and I was able to continue compiling as I was used.

Although this is not a direct solution, it allows me to continue working.

Answer 2

I installed the latest version of SBT on Ubuntu successfully, but indirectly by installing Disafe Stack.

Answer 3

Currently sbt-0.11.3-build-0100 is available (http://apt.typesafe.com/pool/pool/main/s/sbt/), so you can just update it to solve your problem. If this does not work, or if you are curious about the original problem, here is my diagnosis.

As you tried, you need to use the new launcher for SBT 0.11.3 to use the new group identifier, org.scala-sbt . The second error message still shows a failure that refers to org.scala-tools.sbt - this is bad, and assumes that you are actually still using the old launcher.

Could you make sure that when you run sbt you are running the created script, and not the one from the Debian package? Try using the full path to run sbt, for example ~/bin/sbt .

If this helps, you should fix PATH so that ~/bin (or wherever you install your script) comes before the directory where the SBT system is installed, which (I would say, but this is an opinion question) is generally useful .