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.
-
-
tried sbt -no-share compile ?
-
Trying now. This could work... :)
End of conversation
New conversation -
-
-
You can get the classpath with a sbt command. That will list all the runtime deps (we do this on clever cloud)
- End of conversation
New conversation -
-
-
I think coursier has some way of sandboxing dependencies.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.