cached resolution: updateClassifiers with cached resolution is really slow
See original GitHub issueThis impacts multi-module projects in ENSIME and IntelliJ (at least), since anything that requires the sources/docs will need to call updateClassifiers on a per-module basis for export.
e.g. use sbt gen-ensime
on https://github.com/ensime/ensime-server The command is doing this work: https://github.com/ensime/ensime-sbt/blob/master/src/main/scala/EnsimePlugin.scala#L142
Issue Analytics
- State:
- Created 9 years ago
- Reactions:26
- Comments:27 (9 by maintainers)
Top Results From Across the Web
sbt/sbt - Gitter
the script does sbt updateClassifiers on all my branches and then caches the ... is the real problem, not coming up with a...
Read more >SBT on IntelliJ takes a very long to time refresh - Stack Overflow
One thing can help is cached dependency resolution, which is a setting available ... You can read more about updateClassifiers being slow at ......
Read more >sbt Reference Manual — Cached Resolution
Unlike the Scala compiler, Ivy does not have the concept of separate compilation, so that needed to be implemented. Instead of resolving the...
Read more >Opening scala sbt project unbearably slow. : SCL-14200
I can probably fix the multiple resolution issue. Do you think you can fold your caching improvements into the main sbt codebase and...
Read more >Ammonite
The compilation of the predef is cached, so after the first run it should not noticeably slow down the initialization of your REPL....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please consider using the new reaction feature and choosing 👍 there instead of adding another comment.
and if you do that, also Subscribe to the thread for updates (an advantage of the old 👍 technique)