Preserve results of sbt incremental compilation when moving project directory

Question

Consider the scenario: I have a simple scala project managed by sbt, in a directory called foo.

cd foo
sbt compile

It now takes a few seconds and the project compiles correctly.

Now, thanks to sbt incremental compilation, if I run

sbt compile

it terminates the compile task in close to 0 seconds, since the source code hasn't changed.

But if I rename the foo directory into bar

cd ..
mv foo bar

and try to compile it again

cd bar
sbt compile

now the compile task takes again few seconds, hence not using the results from the previous compilation.

Is there a way to preserve the incremental compilation results of a project even when its absolute path on disk has changed?

ok, apparently sbt stores the results of incremental compilation using an absolute path, and that's why it breaks. Now, how to fix it? — Gabriele Petronella, Jan 27 '17 at 13:06
I would use the sbt gitter channel :) this sound like a pretty involved question. — marios, Jan 29 '17 at 01:59

score 2 · Answer 1 · answered Mar 17 '17 at 21:07

2

You can also try to use Hoarder Plugin: https://github.com/romanowski/hoarder.

Ping me on Hoarder's gitter in case of any questions/problems.

answered Mar 17 '17 at 21:07

romanowski

21
2

Thank you! I'm well aware of it, I plan to try it soon! :) – Gabriele Petronella Mar 17 '17 at 21:29

score 0 · Answer 2 · answered Feb 04 '17 at 10:56

As it turns out, there's some work in progress to make incremental compilation results cacheable. Here's the relevant PR: https://github.com/sbt/zinc/pull/216.

Also, there's an issue (being discussed at the time of this writing) about making zinc's analysis completely machine independent. See https://github.com/sbt/zinc/issues/218.

Preserve results of sbt incremental compilation when moving project directory

2 Answers2