I have no details yet how to reproduce this one, but it happened.
After multiple invocations of j2cl:build I have this directory structure:
gwt3BuildCache\0.19-SNAPSHOT\de.xam.example.math-math-lib-0.1.0-SNAPSHOT contains
So it seems the unpack-phase was successfully cached and reused, but lead to two different stripped_sources.
The stripped sources do not differ. Also, the code in unpack (in my case) contains no @GwtIncompatible, hence the stripped sources are the same content as the sources.
What else goes into the hash? Timestamps? For best caching it should be a pure content hash.
I have no details yet how to reproduce this one, but it happened. After multiple invocations of
j2cl:build
I have this directory structure:gwt3BuildCache\0.19-SNAPSHOT\de.xam.example.math-math-lib-0.1.0-SNAPSHOT
containsSo it seems the
unpack
-phase was successfully cached and reused, but lead to two differentstripped_sources
. The stripped sources do not differ. Also, the code inunpack
(in my case) contains no@GwtIncompatible
, hence the stripped sources are the same content as the sources.What else goes into the hash? Timestamps? For best caching it should be a pure content hash.