[ 
https://issues.apache.org/jira/browse/SCM-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961206#comment-17961206
 ] 

ASF GitHub Bot commented on SCM-368:
------------------------------------

jira-importer commented on issue #589:
URL: https://github.com/apache/maven-scm/issues/589#issuecomment-2964605581

   **[Dominique 
Jean-Prost](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=djeanprost)**
 commented
   
   Well, I've just tested as the plugin has been released, and I still meet the 
problem. Here what I do :
   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.
   
   Can you look at this please ?
   
   PS : my test was done by using the release plugin. It failed for the same 
reason, then I tested directly the scm plugin.
   




> Windows path length limitations can be overcome by feeding an absolute path 
> to SVN
> ----------------------------------------------------------------------------------
>
>                 Key: SCM-368
>                 URL: https://issues.apache.org/jira/browse/SCM-368
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-scm-api
>    Affects Versions: 1.0
>         Environment: Any Windows machine
>            Reporter: Kurt Tometich
>            Assignee: Emmanuel Venisse
>            Priority: Minor
>             Fix For: 1.1
>
>
> 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.  Here is a link to the forum where I found this 
> information: http://en-us.www.mozilla.com/en-US/firefox/2.0.0.4/firstrun/.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to