Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Artifact resolution is unreasonably slow for multi-module projects
See original GitHub issuenote from sbt team
This issue is now solved using cached resolution feature.
updateOptions := updateOptions.value.withConsolidatedResolution(true)
If anyone has further issues with dependency resolution performance, please provide more context and open a new Github issue.
original report
So I have a multi-module project - dozens of modules - in which many of the modules have very similar (transitive) dependencies. Each day, sbt (v0.11.2) decides it needs to re-check all those dependencies, and it does so independently for each module. So if I have, say, 20 modules depending on slf4j, sbt appears to hit the repository 20 times to re-download exactly the same pom.xml. Multiply that by a hundred-odd dependencies and the whole process is taking a couple of minutes. Seems like some caching or up-front reconciliation would be helpful here.
Issue Analytics
- State:
- Created 11 years ago
- Reactions:4
- Comments:76 (38 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Almost 4 years passed… Look guys, are you serious about SBT at all?
I’ve solved that by watching cats on youtube during resolution: https://www.youtube.com/watch?v=UIrEM_9qvZU.