Windows path length limitations can be overcome by feeding an absolute path to
SVN
----------------------------------------------------------------------------------
Key: SCM-409
URL: http://jira.codehaus.org/browse/SCM-409
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-api
Affects Versions: 1.1
Environment: Windows OS
Reporter: Dominique Jean-Prost
When calling Subversion with relative paths there is a limit of 255 characters
to the path length. If you call Subversion with an absolute path that no longer
applies and you now have access to 32K chars. I have tried this myself and it
does work. Try feeding SVN a path that is relative and is over 255 chars. It
will not be able to complete the transaction. Now, try to the same path again
only as an absolute path and it will successfully complete the transaction.
This bug was originally fixed for the update command, but still remains for the
checkout command. There may be other command that are affected by this bug.
1. cd c:\a\very\long\paht\under\windows\xp\or\windows\2000
2. mvn scm:checkout -DconnectionUrl=scm:svn:http://myUrlHere
--> It says
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout
http://myUrlHere checkout"
[INFO] Working directory: c:\a\very\long\paht\under\windows\xp\or\windows\2000
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: Your .svn/tmp directory may be missing or corrupt; run 'svn
cleanup' and try again
svn: Can't open file 'checkout\blabla....svn-base': Le chemin d'accès spécifié
est introuvable.
3. If I execute svn --non-interactive checkout http://myUrlHere
c:\a\very\long\paht\under\windows\xp\or\windows\2000\checkout : it works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
