[GRADLE-3555] ClassNotFoundException when resolving external dependency Created: 12/Sep/16  Updated: 20/Dec/16  Resolved: 20/Dec/16

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 3.3-rc-1

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Fixed Votes: 1

Known Issue Of:


The detailed discussion can be found on the Gradle forum.

After an upgrade of the Gradle version, the user is seeing a ClassNotFoundException for an external dependency. The issue can only be resolved if the Gradle cache is deleted.

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 Daniel Lacasse (Inactive) [ 20/Dec/16 ]

As per discussion in this blog post, the issue was reported as fixed.

Generated at Wed Jun 30 12:51:51 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.