A workaround is to move the root of your Gradle source code clone to a higher position in your filesystem.
If you run Windows >=10 or Windows Server >= 2016, another workaround is to disable that limit, see http://stackoverflow.com/a/27694470
Ok, I know the 260 limitation, but the gradle generated file is 229 characters by itself which lets few bytes for a normal prefix… I was expecting a ligther workaround than moving my git project under C:
I am running gradlew :platformNative:check for validating a Push Request for the support of vs2015. Would it be acceptable for the Gradle team to bypass this test for delivering the changes?
the gradle generated file is 229 characters by itself which lets few bytes for a normal prefix…
That’s true
I am running gradlew :platformNative:check for validating a Push Request for the support of vs2015. Would it be acceptable for the Gradle team to bypass this test for delivering the changes?
Sure, you can temporarily @Ignore that particular test on your end so you can run :platformNative:check without hitting this issue.