[GRADLE-3252] AbstractFileResolver produces org.gradle.api.UncheckedIOException when path is too long on Mac OSX Created: 02/Mar/15 Updated: 10/Feb/17 Resolved: 10/Feb/17
Found on Gradle 2.2.
I'm seeing an org.gradle.api.UncheckedIOException thrown from AbstractFileResolver on Mac OS X 10.9 when I try to run a particular Test task in my project. getCanonicalFile() throws an exception because the submitted class path is too long.
Seems to be coming from this optimization in AbstractFileResolver:
// Short-circuit the slower lookup method by using the canonical file
I was able to work around the issue by enclosing the block above in a try-catch, so AbstractFileResolver.normalize() proceeds with the 'slower' lookup in the case of an IOException here.
Would recommend including something along those lines in the next release in case anyone else runs into this issue.
|Comment by René Gröschke (Inactive) [ 02/Mar/15 ]|
This is reproducable via:
|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.