Hendrik Maryns schreef:
> Mark Phippard schreef:
>> On Tue, Jun 10, 2008 at 12:26 PM, Hendrik Maryns
>> <qwizv9b02_at_sneakemail.com> wrote:
>>> I have some symbolic links to directories under version control. I
>>> had to
>>> resort to the command line to commit them, since Subversion
>>> wouldn't. Now
>>> it shows them with the 'edited' star all the time, even though the files
>>> beneath them are up to date.
>>> Directory structure:
>>> project/src/<my java files>
>>> _______/bin/<eclipse puts class files here>
>>> _________________/Linux/makefile (same for Windows and Mac)
>>> __________________/link to makefiles
>>> __________________/link to src
>>> __________________/<other files needed for building, such as README>
>>> _______/<build script and other stuff>
>>> All of this under version control.
>>> After a commit, src is free of change markers, but the link below
>>> has one. It points at files which were changed once (probably at the
>>> time I
>>> committed the link), but no longer now.
>> Are you using JavaHL? I know SVNKit has historically had a hard time
>> dealing with symlinks properly.
>> Subclipse just relies on information we return from the SVN API's we
>> are calling.
> I use SVNKit indeed. JavaHL is not available. I’d rather not install
> it, but if this bothers me too much, I’ll give it a try.
I just wanted to mention that I see similar behavior with JavaHL: in
some subfolder, there are some files that are created by SWIG. I have
marked them as derived, and Subclipse ignores them, as expected.
However, in the same folder reached via the symbolic link, they are
still marked with question marks. Marking them as derived there doesn’t
Ask smart questions, get good answers:
Received on 2008-06-26 13:58:48 CEST