[GRADLE-413] Cached build file is not recompiled when build classpath changes Created: 23/Feb/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


For example, say I have a build script which references a class by fully qualified name:


and I forget to add this class to the build classpath. When I run this build, it will fail, complaining that 'com' is an unknown property.

If I then add the class to the build classpath, the build continues to fail in the same way, as the cached build file is still being used. Rebuilding the cached build file fixes the problem.

Comment by Hans Dockter [ 07/Apr/09 ]

Getting rid of settings.gradle would solve this problem, wouldn't it?

Comment by René Gröschke (Inactive) [ 29/Oct/15 ]

no it wouldn't. We hit this issue regulary also in gradle training classes by following these steps:

1. have a build.gradle declared and don't touch it anymore
2. add a buildSrc project
3. -> buildSrc classes are not picked up in build.gradle file.

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:29:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.