[
https://issues.apache.org/jira/browse/SCM-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961204#comment-17961204
]
ASF GitHub Bot commented on SCM-368:
------------------------------------
jira-importer commented on issue #589:
URL: https://github.com/apache/maven-scm/issues/589#issuecomment-2964605591
**[Ovidiu
Predescu](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ovidiu)**
commented
Just an observation, I found cases when cygwin svn fails with absolute
cygwin paths, if those paths are specified in a --targets file. More details
about these cases here:
http://mail-archives.apache.org/mod_mbox/maven-users/200907.mbox/%[email protected]%3E
I'd suggest making using relative paths configurable from pom.
> 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)
