[
https://issues.apache.org/jira/browse/SCM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961346#comment-17961346
]
ASF GitHub Bot commented on SCM-409:
------------------------------------
jira-importer opened a new issue, #627:
URL: https://github.com/apache/maven-scm/issues/627
**[Dominique
Jean-Prost](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=djeanprost)**
opened
**[SCM-409](https://issues.apache.org/jira/browse/SCM-409?redirect=false)** and
commented
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.
---
**Affects:** 1.1
**Issue Links:**
- [SCM-368](https://issues.apache.org/jira/browse/SCM-368) Windows path
length limitations can be overcome by feeding an absolute path to SVN
- [SCM-555](https://issues.apache.org/jira/browse/SCM-555) paths reported in
svn-exe checkout do not match update command (always reports absolute)
> Windows path length limitations can be overcome by feeding an absolute path
> to SVN (checkout command)
> -----------------------------------------------------------------------------------------------------
>
> Key: SCM-409
> URL: https://issues.apache.org/jira/browse/SCM-409
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.1
> Environment: Windows OS
> Reporter: Dominique Jean-Prost
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.2
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
