On 16.09.2014 11:12, Bert Huijben wrote:
>
>> -----Original Message-----
>> From: Geoff Field [mailto:Geoff_Field_at_aapl.com.au]
>> Sent: maandag 15 september 2014 01:38
>> To: Stefan Sperling; Milan_Plancik_at_swissre.com
>> Cc: users_at_subversion.apache.org
>> Subject: RE: svn command line client 1.8.8 - Error: file name or extension
> is
>> too long
>>
>>> On Fri, Sep 12, 2014 at 11:29:37AM +0200,
>>> Milan_Plancik_at_swissre.com wrote:
>>>> Dear team,
>>>>
>>>> I tried to commit my changes with following error message:
>>>>
>>>> Error:Cannot run program
>>> "C:\srdev\tool\SVN_CLIENT_1.8.8\svn.exe" (in
>>>> directory
>>>>
>>> "C:\Users\S3F96Q\work\sources\g10ct\SR_G10_CT\modules\sr-g10-c
>>> t-batch-xd\src\main\resources"):
>>>> CreateProcess error=206, The filename or extension is too long
> Going back to the original error report:
>
> Looking at the error(CreateProcess error=206), you get this error when
> starting the process, not after the process started.
>
> This implies that the length problem is either with the name of the process
> (=svn.exe) or with the directory in which you are trying to start the
> process.
>
> If the path length error would have been in an argument, or a subpath you
> would have received an error from svn, not from the process starting svn.
>
> In general Subversion 1.7 and later shouldn't have problems with long paths,
> as long as all the (long) passed paths are in the absolute form.
>
> Long relative paths have different problems, as the Windows api to transform
> those paths to their absolute form doesn't support long paths.
>
>
>
> You can probably solve your issue by just starting 'svn' explicitly from
> 'C:\' or some other safe directory.
See above; the OP used IntelliJ IDEA, which drives the command-line
client, not the command line directly. I suspect it's a limit of the
CreateProcess API, which limits the command-line paraneter to MAX_PATH;
so, if there are a lot of files to commit, and IDEA (correctly) passes
absolute paths to Subversion, it's fairly easy to exceed that limit.
This is just guesswork, of course, but I've seen similar things happen
in naïvely written apps on Windows. To make things worse, the IntelliJ
devs probably don't have much control over how Java launches external
processes on Windows.
-- Brane
Received on 2014-09-16 12:08:01 CEST