Last week we had the user directory permissions changed on our CI servers and we no longer have write access to the user home directory. Hence sbt fails to boot because it
The ivy path options mentioned in the other answers here were part of the solution. As pointed out in this answer you need to set ivy for both sbt itself and the project. Furthermore as I discovered on this sbt github issue comment, sbt needs yet another directory for its own stuff.
In total, I used the following three jvm properties in order to use a relative path to the project for everything that sbt otherwise uses the user's home directory for:
-Dsbt.global.base=./.sbt/
-Dsbt.ivy.home=./.ivy2/
-Divy.home=./.ivy2/
At least as of sbt 0.13.9, this is what is needed.
If you would like to run with your .ivy in a different location, and you're using sbt extras boot script, then you should just be able to do:
sbt -ivy /path/to/ivy package
and it'll download all the ivy stuffs to the location specified and run whatever command you need (in this example, package)
You can set -ivy when using sbt-extras (preferable), or you can use a JVM property:
-Dsbt.ivy.home=/path/to/ivy
I've also used this:
-Divy.default.ivy.user.dir=/path/to/ivy