Mark Phippard wrote:
>> Apparently there is a workaround for that in Subversion FAQ
>> http://subversion.tigris.org/faq.html#long-paths
>>
>> It even work from Subclipse, but only if I don't use default workspace
>> location and specify absolute path where project should be checked out.
>> So, it seems like this error happen because Subclipse is using path like
>> C:/fooo/boo instead of true Windows paths like C:\fooo\boo, but if I
>> manually specify path like the latter one pointing to the workspace
>> location, Subclipse fail to create project on checkout. Is there any way
>> to address this?
>>
> I do not think it is an issue of C:\ vs. C:/. Internally, all paths
> are converted to the latter before calling the API anyway.
> Subversion's API requires this. The issue more likely is that a
> relative path is being used in one scenario and an absolute in the
> other. I am a little surprised it would ever use a relative path in
> Subclipse though as we have no control over the CWD.
>
> So consider me perplexed.
>
It is strange then, I thought that svn command line client is using
the same Subversion API, but it does allow using C:\
Something seem disconnected there.
> Are you using JavaHL or SVNKit?
JavaHL and it is also the same with the latest Subclipse 1.3.x
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-01-18 19:45:14 CET