[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: connecting existing SVN projects which are symlinked

From: Edward Rudd <eddie_at_omegaware.com>
Date: 2005-04-07 22:51:30 CEST

On Thu, 07 Apr 2005 15:47:29 -0400, Mark Phippard wrote:

> news <news@sea.gmane.org> wrote on 04/07/2005 03:39:42 PM:
>
>> On Thu, 07 Apr 2005 14:25:55 -0400, Mark Phippard wrote:
>
[snip]
>
> The Eclipse feature I am describing does the exact same thing, it just
> doesn't use symlinks. I can create a WC with a bunch of projects checked
> out into it. In Eclipse when I import them it is essentially just
> "registering" them to my workspace. Nothing moves. With Eclipse 3.1 and
> Subclipse 0.9.29 when you do this it will even automatically "share the
> project" with Subclipse. Also, if you add a new project and you place it
> in this master WC location, it will even auto-add it to Subversion for
> you.

Which I have just done this. and it actually didn't complain that there
were symlinks of the same name in the workspace directory :). as I still
work in a term as well as in a gui.

[snip]

>
> Subclipse itself doesn't really do anything with your files and folders.
> We just make Subversion API calls. Subclipse should not be in the
> business of figuring this stuff out. Bring it up on the Subversion
> mailing list and convince them to make the API follow the symlink.

I will be doing that, though I still feel this issue is FAQ worthy and
should be placed on the main website.

Edward Rudd
Received on Fri Apr 8 06:51:30 2005

This is an archived mail posted to the Subclipse Users mailing list.