[GRADLE-1052] Gradle sometimes does not rebuild out-of-date classes which have been built by other Gradle versions and external tools Created: 24/Jul/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Won't Fix Votes: 0


There's a few related problems:

  • The source files have not changed since the classes were built, but the compile classpath has changed (eg a snapshot has changed or the Gradle API has changed in the case of buildSrc). Gradle will attempt to run the compile task, but the ant task will decide that nothing has changed and compile nothing.
  • The source files have changed since the classes were built. The ant task will compile the modified files. However, Gradle will not remove any stale class files or resources, and so dependent files will not be recompiled.
  • The source files have not changed, but the settings have (eg debug, compiler version, etc).

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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