These are chat archives for sbt/sbt-assembly

28th
Dec 2017
Ghost
@ghost~540393fe163965c9bc2018ce
Dec 28 2017 14:41
is there a way to run assembly such that it uses a cached version of the jar if no inputs have changed?
I'm building an alternative sbt-proguard on top on sbt-assembly so it restricts proguard to only doing the optimisations / trimming rather than the jar building too
but it means that every time I run my task, the assembly jar is being rebuilt, even though there are no changes
Ghost
@ghost~540393fe163965c9bc2018ce
Dec 28 2017 15:00
I'm using FileFunction.cached around Set(assembly.value) but because assembly.value always creates the fat jar, it is not doing what I want.
I see cacheOutput = true is the default, I've not changed this... so it doesn't appear to work as advertised
Ghost
@ghost~540393fe163965c9bc2018ce
Dec 28 2017 16:03
seems the cache works but only after the jar is built TWICE. There is definitely something fishy going on