Currently plugins don't have access to the list of changed files (input and
output) that triggered Gradle to re-run a task.

The Android plugin is adding several steps to the compilation, and we'd
like to make sure that we can do them as incremental steps. We could
replicate what Gradle already computes but this seems silly as Gradle
already has the data.

Any chance this will become part of the official API?

We are also looking at some tasks that would require storing some
information somewhere to improve speed when running the task incrementally.
I see there are some things stored inside .gradle/<version>/taskArtifacts
and I was wondering if plugin can get access to this (or just simply write
directly to it).

thanks

Reply via email to