Wonders never cease. :)
Using 0.9.105 in 3.1.1 on Windows I just noticed an odd display bug in the
Synchronize view where suddenly a project is nested into itself as
modification. Selecting either the parent or itself as child does not seem
to make a difference for commit; in either case the /top-level project is
slated for commit. Cleanup, restarting eclipse or handwaving do not help.
The command-line tools show only the regular top-level directory as
modified so things are not 'really' messed up; it only seems to be a
display bug.
I *think* it can be reproduced by:
- adding resources to svn:ignore
- adding more resources to svn:ignore *outside* of eclipse (>20 projects,
had to do some mass-ignoring via TortoiseSVN)
- refresh Synchronize view
This is with JavaSVN; I cannot test right whether it also happens with JavaHL
since my repo uses svn+ssh and I don't have that configured properly.
Might be able to try later.
It is also not the first time I've seen this; it seems to go away and
everything works as usual after commit.
sorry to be such a pest :-)
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 24 17:41:46 2006