Kind of benchmark of sbt-coursier against default sbt 1 resolution. Run it locally, and tell us your results!https://github.com/alexarchambault/coursier-benchmark …
I'm sure @alxarchambault knows this, but basically every Ivy resolution with SBT seems to involve a 302 redirect to another 302 which leads to a 404, for a couple of resolvers before getting a 200. Those 302s and 404s (as per protocol) don't get cached.
-
-
Only one repository (Central) should be involved in the benchmark project, which should limit these kind of failed attempts. That said, I haven't checked whether sbt checks other repositories too here (might be good to ensure that it doesn't).
-
I was trying to improve downloads at Scala World, so with a "default" configuration, I ran SBT through a proxy server, and noticed about 6 HTTP requests to various repositories (e.g. typesafe) before fetching most files. I think this is typical.
- Show replies
New conversation -
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.