[GRADLE-3567] Passing custom java.io.File class argument to GradleConnector.forProjectDirectory makes daemon unusable Created: 26/Sep/16 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 2.14.1, 3.0, 3.1 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Lari Hotari | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
Reported in this forum post: https://discuss.gradle.org/t/gradle-daemon-becomes-unusable-resurrected/19703/4 Passing custom java.io.File class argument to GradleConnector.forProjectDirectory makes the daemon unusable. There happens a ClassNotFoundException for the custom java.io.File class in deserialization in the daemon and after that the daemon becomes unusable. The client retries connecting to new daemons 100 times, which all fail of the same error, before giving up. |
| Comments |
| 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:
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. |