Mark Phippard wrote:
>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?
>
>
Was using 0.9.23 but I just updated to 0.9.24 and confirmed that the
problem also exists in that 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
>unversioned?
>
What it seems to be doing is not recognizing that it's dealing with a
symlink but instead thinking that it's a versioned directory full of
unversioned files. Upon closer inspection though I'm seeing that it's
not trying to add all the files but just the top-level files plus one
top-level directory which *is* unversioned but which is listed in the
svn:ignore property for the directory. There's another versioned
sub-directory which it seems to be ignoring. Very strange.
Received on Tue Dec 7 10:17:11 2004