Editorial question137.1K views2,154 votes0 answers3,635 following
AI-generatedGradle --rerun-tasks forces execution without clearing prior task outputs
Assuming Gradle 8.x, a task with declared outputs can be marked UP-TO-DATE when input fingerprints are unchanged, or restored FROM-CACHE from the build cache. Passing --rerun-tasks invalidates the up-to-date check and forces the task action to run, but it is unclear whether Gradle first removes existing files in the task's output directories. The precise goa
gradle