Reputation: 5139
Similar problem with How to use sbt behind authenticated proxy?. I tried with the given answer and problem still there.
When I run sbt in terminal, it shows and stucks at :
Getting org.scala-sbt sbt 0.13.6 ...
additional information:
sbt --version
sbt launcher version 0.13.6
How could I fix it?
Upvotes: 129
Views: 55327
Reputation: 1
I faced the same problem of sbt getting stuck on "getting org.scala-sbt sbt 1.4.7 (this may take some time)...". I resolved this problem by commenting the $JAVA_HOME variable in bashrc, and restarting the terminal. You can also ensure that the JAVA_HOME is not set by running echo $JAVA_HOME
. Subsequently, rerun the sbt command with -v
flag (for verbosity). After running the command, you should observe prints after "getting org.scala-sbt sbt 1.4.7 (this may take some time)..." line.
Upvotes: 0
Reputation: 1665
There is an update log ...
$ tail -f $HOME/.sbt/boot/update.log
Execute the above command in another terminal to see the progress. Using -v option works as others already indicated as well.
Upvotes: 49
Reputation: 4483
It's quite a late answer, but I encountered the same problem working behind a proxy. If this is your case, you should run export JAVA_OPTS="$JAVA_OPTS
-Dhttp.proxyHost=<your-proxy> -Dhttp.proxyPort=<your-proxy-port>"
before running sbt
.
If you are still unsure if it's going ahead with the downloading, you should try launching sbt
with the verbose option sbt -v
, as suggested by @evan912. If you had a problem with the proxy, after setting it you should see some [info] downloading
logging on your console.
Upvotes: 4
Reputation: 21
try to use a fast maven mirror or run it behind a http/https proxy .
Upvotes: -3
Reputation: 2339
This is quite old post and my answer may not be completely relevant. But here is my experience:
So my solution is that you have to wait a bit.
Upvotes: 219
Reputation: 179
I think sbt takes some time to download its jars when it is run first time. That is why it seems to be stuck. It works normal after the download is completed.
Upvotes: 9
Reputation: 8021
Creating a build.sbt file worked as well. My build.sbt file looks like below;
lazy val root = (project in file(".")).
settings(
name := "hello",
version := "1.0",
scalaVersion := "2.11.4"
)
Upvotes: 1
Reputation: 5139
I bypassed the error by adding a build.properties file under project folder, in which, I put:
sbt.version=0.13.5
I think this probably is because my system has activator pre-installed instead of sbt, which is easier to work with play project. Not quite clear in the theory as I just start to use sbt.
Upvotes: 13