I think that, at its core, is how gradle's cache i...
# klaxonj
jlleitschuh
09/14/2018, 8:34 PMI think that, at its core, is how gradle's cache invalidation works today.
That's what all the annotations on a gradle task are doing. Telling gradle what the inputs/outputs are.
I think gradle chose to do the cache by default for tests because it would speed up builds for a majority of use cases but allowing the flexibility to disable it if nessasary.
What external inputs does Klaxon have that makes it not fit the general use case where tests can be cached??