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

Re: bug: symbolic links not recognized as such

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-12-06 20:28:24 CET

Jeff Bowden <jlb@houseofdistraction.com> wrote on 12/06/2004 01:36:08 PM:

> Sorry if this is the wrong forum but I couldn't figure out how to enter
> a bug report in the issue tracker so here goes:
> Subclipse doesn't properly handle symbolic links. I have a project with

> some symbolic links under version control. Subversion itself handles
> this just fine but subclipse keeps wanting to commit files it finds
> through the symlink even though they are already versioned under another

> directory. In case that's not clear, here's an example:
> trunk/Project/foo/blahblah.txt
> trunk/Project/bar/foo-inst -> ../foo
> that is, foo-inst is a symlink which points to foo. If I checkout
> Project and run svn status on the working copy it says everything is
> up-to-date, but if I right-click on Project in eclipse and select Team |

> Commit... it says Project/bar/foo-inst/blahblah.txt is an unversioned
> resource and wants to add it to the repository.

What is the Subclipse version?

Could you describe what you think it is doing? If I had to guess, I would
say that it is following the symlink to the target and seeing that file as


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Tue Dec 7 06:28:24 2004

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.