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

Re: [Subclipse-users] Synchronize view woes

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-09-08 19:04:18 CEST

Christian Sell <christian.sell@netcologne.de> wrote on 09/06/2006 04:26:16
AM:

> this is an issue that has existed for a long time, and thus may have
been
> discussed previously:
>
> when symlinks exist inside the versioned source tree, the synchronize
view
> behaves strangely:
>
> I have a non-versioned directory inside the versioned tree (its in
svn:ignore of
> its parent) which holds a symlink to a versioned sibling directory.
Thus,
> inside symlinked directory, there exists the .svn machinery.
>
> rootdir<versioned, svn:ignore=subdir2>
> subdir1<versioned>
> subdir2<not versioned>
> symlink->subdir1
>
> Now, when I call up the synchronize view, It takes a long time to open,
as it
> inspects the whole symlinked subtree, and afterwards it shows the
contents of
> subdir2/symlink->subdir1 as newly added files. There seems to be no way
to get
> around this.
>
> Interestingly, if I call up the commit dialog directly from the package
browser,
> it does not show these files.

You might give JavaHL a try to see if we can narrow it down to an adapter
problem or a Subclipse problem. I know that JavaSVN has had some
difficulties in dealing with symlinks correctly. Also, there is a
property you can set to turn off the symlink handling that it does
include. It has often been recommended that people set this property to
correct performance problems. You might just review that you did not set
this property. I think it would an Eclipse JVM startup property.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 8 19:04:41 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.