You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/09/04 08:38:00 UTC
[jira] [Created] (LUCENE-9505) Gradle tasks with
outputs.upToDateWhen {true} are hard to re-run in separation
Dawid Weiss created LUCENE-9505:
-----------------------------------
Summary: Gradle tasks with outputs.upToDateWhen {true} are hard to re-run in separation
Key: LUCENE-9505
URL: https://issues.apache.org/jira/browse/LUCENE-9505
Project: Lucene - Core
Issue Type: Task
Reporter: Dawid Weiss
Assignee: Dawid Weiss
We have several tasks that only have inputs and no outputs. For incremental builds, this means that they are only re-run if:
* the inputs change,
* --rerun-tasks is given on command line.
Gradle has a built-in rule for "cleaning" the outputs of a task - a "clean[TaskName]" rule, so in theory you could clean the outputs of a single task and re-run the entire build with only that task being re-run. It would be sometimes convenient.
We could add a dummy output to these tasks instead of upToDateWhen (for example, touch an empty file at the end of the task's execution). Then cleanXXX should work for them (and so would incremental builds).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org