Please review your inputs and outputs, especially with multiple target platforms

[Vampire]

I've found at least two places where changing / deleting the output did not make the task out-of-date or changing an input did not make the task out-of-date.

Please review the input and output annotations as this leads to unreliable builds and also prevents from ever being able to make any of the tasks cacheable. And it also make it harder to use the tasks as input for other tasks.

The one places over which I stumbled where, that the runtimeZip task does always declare the non-targetPlatforms file as output and never the targetPlatform specific ones. This for example caused that the task was up-to-date even after I deleted the output files and that tasks.githubPublish { from(tasks.runtimeZip) } caused the artifacts to be built, but not uploaded until I added the outputs via the runtime API.

The other place was, that changing the runInBinDir property did not make the startScripts task out of date. After changing it to true, rebuilding and testing, the behavior didn't change and I first had to find out that it is the normal startScripts task of the application plugin you use to fix that up.

[gotson]

changing the runtime.modules will not mark the runtime task outdated either.

[dsilvasc]

Here's a workaround for the case @gotson mentioned:

// Workaround for https://github.com/beryx/badass-runtime-plugin/issues/104
// The jre task correctly re-runs when we update the list of modules to include,
// but the runtime task incorrectly remains up-to-date.
tasks.named("runtime").configure {
  inputs.files(tasks.named("jre"))
}

[TheoLassonder]

@dsilvasc Thanks for the work around!