maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] Reopened: (SCM-368) Windows path length limitations can be overcome by feeding an absolute path to SVN
Date Tue, 20 May 2008 22:47:27 GMT


Olivier Lamy reopened SCM-368:

The fix in rev [656441|] breaks continuum
on cygwin.
Relevant part of the log :

2008-05-21 00:28:26,265 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager
.Slf4jScmLogger  - Executing: cmd.exe /X /C "svn --non-interactive update C:\ci\wd\41"
2008-05-21 00:28:26,296 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager
.Slf4jScmLogger  - Working directory: C:\ci\wd\41
2008-05-21 00:28:26,484 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager
.Slf4jScmLogger  - Svn command failed due to some locks in working copy. We try to run a 'svn


The workaround is too add windows svn first in the cygwin path.

> Windows path length limitations can be overcome by feeding an absolute path to SVN
> ----------------------------------------------------------------------------------
>                 Key: SCM-368
>                 URL:
>             Project: Maven SCM
>          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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message