Here are the various situations I have come across with Sym Links with
the JavaSVN library.
1. Where a sym link points to another directory in the same working
copy, the directory is marked as having changes the files below the sym
link are shown as being unversioned files in the project browser and in
the synchronize view.
2. Where a sym link points to another directory in a working copy of
another SVN managed project, the same above problem occurs.
3. Where a sym link point to another directory and the target of the sym
link does not exist the sym link will be shown as a new file from the
repository in the synchronize view.
On Wed, 2006-02-15 at 21:12 -0500, Mark Phippard wrote:
> > Just tried the latest version of subclipse with JavaHL and it now seems
> to work fine. I presume
> > JavaSVN has difficulty checking to see if it is a sym link as it's pure
> > Any chance that an entry could be added to the subclipse FAQ about using
> JavaHL if you use sym > links?
> If it comes to that, sure. But Alex has put a lot of effort into getting
> symlinks working correctly with JavaSVN. I think the issue is just that
> there are a lot of different corner cases to deal with. So it would
> probably help if you could just provide as much detail as possible about
> your setup so that he can test it. From what you said before, I think it
> was this:
> You have a symlink to a folder inside a working copy, and that symlink is
> pointing to another folder that is also a valid working copy.
> Based on the Issue you cited, it sounds like the command line, when svn
> status is run, would just completely ignore the symlink. It sounds like
> JavaSVN does not.
> Feel free to re-explain in your own words.
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Thu Feb 16 18:25:25 2006