SCSS compilation breaks watcher assumptions about cryogen-core HOT 7 CLOSED

The checksum approach would probably the most robust, since something similar could happen again in the future.

from cryogen-core.

@yogthos I agree. Unless you or @lacarmen already have a plan, I'll see if I can do something about this.

There's a bit more to this though I think. Maybe doing scss compilation before copy-resources and making them dependent on a different set of checksums (scss files and not scss files would be a good start) would help the 2 pass problem.

from cryogen-core.

@j0ni @lacarmen I think this one's all yours if you have a plan already :)

from cryogen-core.

Looks like the infinite loop was actually a bug in my code, and since the sass compiler was writing to the resources/public directory, my explanation of the double compile thing was likely wrong.

I can only surmise that the sass compiler drops some tmp files into the source directory, or otherwise causes the modified times to be updated. Otherwise I can't see why it was happening. Either way, using checksums rather than modified times made it stop.

from cryogen-core.

I just pushed out 0.1.11 to clojars :)

from cryogen-core.

Can we close this one now?

from cryogen-core.

yep :)

from cryogen-core.