IssueTracker

AndroidLintTask lists the lint baseline file (e.g. lint-baseline.xml) as an @InputFiles property, but the file is also functioning as an @Output of the task, since Lint, as documented here, re-generates the baseline file if one doesn't exist.

This isn't good practice in Gradle, and leads to some odd behavior.

For instance, if you:

1. run gradlew app:lint -Dlint.baselines.continue=true, generating a new baseline file
2. immediately delete the new baseline file
3. re-run gradlew app:lint -Dlint.baselines.continue=true

The baseline file is not re-created, since Gradle observes the same "before" state for both invocations and marks the task as Up-To-Date (Gradle doesn't include the file in the "after" snapshot for the task because the file isn't marked as an @Output). A fix/workaround is pending for this particular issue, but there may be other issues inherent to this non-idiomatic use of the Gradle API.

This comment proposes a fix in AGP for the broader issue.