[GRADLE-1312] Most tasks of typical Java/Groovy project are never up-to-date Created: 17/Jan/11  Updated: 04/Jan/13  Resolved: 23/Jan/11

Status: Resolved
Project: Gradle
Affects Version/s: 0.9.1
Fix Version/s: 0.9.2

Type: Bug
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Fixed Votes: 0


It seems that with 0.9.1, most tasks of a typical Java/Groovy project (including compile and test) are never up-to-date anymore. This is in stark contrast to 0.9, where most tasks are up-to-date on subsequent runs (if nothing has been changed). I can reproduce this for the Spock project, but I've also observed it in another (closed-source) project. It appears that compile is rerun because Gradle believes that some dependencies have changed, and test is rerun because Gradle believes that something in the environment has changed.

Generated at Wed Jun 30 11:52:21 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.