Java code to be compiled knows when an individual class file has been deleted,
or that it's older than a modified source file.
In attempting to replicate this behavior from say a single file that generates
code and/or resources, there does not seem to be a clean way to model this with
just @OutputFile to be able to take advantage of the up-to-date checking.
Short of messing directly with the TaskOutputs property/variable, is there any
other way to model this, short of pointing at a top-level directory and playing
with the upToDateWhen closure?
-Spencer
