sbt VS bloop

After spending one day or two reading documents and many frustrated attempts to fix the issue, I ended up arriving at this Github - Spurious recompilation in multi-project build This was not the fix itself, however, gave me light by the end of the tunnel to understand the problem was indeed with the multi project setup.

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇

Sbt has the primitives that would allow that, but this would change the semantics of the test task. See also testQuick and https://github.com/sbt/sbt/issues/6292

If I use IntelliJ then apparently sbtn is not supported and they don't bother with Scala-CLI or Coursier.

Version 1.3.13 has a size of 1.17 MB in zip

See scala-xml 2.x mega tracker on plugin ecosystem conflicts.

This is under discussion at https://github.com/sbt/sbt/issues/6997

See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.

BTW, if you're curious, it appears OP is using this: https://github.com/sbt/sbt/releases/tag/v1.6.2 Pretty sure one of the executables is doing ANSI colours.

If you see the progression of documentation changes over the years pushing people towards multi-project style, and issues like https://github.com/sbt/sbt/issues/6217, hopefully you'd see that I've really tried to encourage people to use multi-project style from the get go.

Here's the links: * bloop: https://scalacenter.github.io/bloop/ * terminal to IDE (iTerm only): https://alexn.org/blog/2021/07/18/iterm-open-file-cmd-click-ide-semantic-history.html * Switching between JetBrains' and standard typechecker in IDEA: Options -> Languages and Frameworks -> Scala -> Editor tab -> Error highlighting

If you look at the Build Tools section of the Metals documentation, you'll see how Metals supports sbt. It is admittedly a bit of a roundabout process: Metals first imports the sbt build definition into a tool called bloop that implements the Build Server Protocol that Metals relies on for metadata, compilation, etc. for the project.

Jorge Vican had finished some work on this in the past, but this feature was abandoned (for now). As u/tgodzik has pointed out, there is not enough interest for this in the community (thanks for replying btw.).

Bloop -- https://github.com/scalacenter/bloop