-
-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems checking out the develop branch on Windows (Filename too long) #259
Comments
@sschuberth Thanks. This is an easy fix. I am surprised this was not caught by the test runs on appveyor |
That's probably because AppVeyor clones to a directory that is closer to the root. But as soon as you have some directories in between you'll exceed the path limit. |
@sschuberth This should be fixed now. Could you give it a shot? |
Works for me now, thanks! |
I'm again having a problem with this, the offending paths being
Do you see a change to shorten these paths again, too? |
@sschuberth sorry I had missed your comment here. The difficult thing is that I was trying to reproduce a faithful maven directory tree. But I guess this could put in a tarball to avoid problems. Or just mock shorter paths in this only case. |
It's probably not worth to address the issue if I'm the only one having these problems (due to the long path name of the parent folder I use for my GitHub projects). Also AppVeyor CI passes. I've anyway worked around this by now by using a shortcut from my usual path to a special short path for ScanCode. So I'll just close this again, but it's still good to have this conversation for the record. |
* path length limitations may prohibit a clean git checkout when the clonning directory hass already some depth. Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
well I committed a quick fix anyway before seeing your comment ;) |
I'm having trouble checking out the
develop
branch on Windows:While I agree this Windows-specific limitation is annoying, is there some easy fix to shorten the path? The part
com/google/collect/com.springsource.com.google.common.collect
looks somewhat redundant.The text was updated successfully, but these errors were encountered: