Is there a less horrific way to fetch all the dependencies of an sbt project than to delete .ivy2, run the build, then copy all the newly-downloaded jars in the newly-created .ivy2 directory?
-
Show this thread
-
By the way, I know that resolving the dependencies by hand is an option too. That's what I was doing until I had the .ivy2 idea.
3 replies 1 retweet 0 likesShow this thread -
Replying to @propensive
You can get the classpath with a sbt command. That will list all the runtime deps (we do this on clever cloud)
2 replies 0 retweets 2 likes -
Replying to @clementd @propensive
Oh maybe I've misunderstood. You want to force the download of all dependencies or just get all of a project's dependencies?
1 reply 0 retweets 0 likes
Replying to @clementd
If they're already downloaded locally, I'll use them. I don't mind downloading them again, though. I just need them all in one place, modulo some scripting.
10:09 AM - 16 Jan 2018
from Marrakesh Medina, Morocco
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.