Mark -
I took your suggestion and switched to the JavaSVN interface preference
and established a new connection to my repository via the svn://
protocol. I then checked in everything out of date and exited from
Eclipse. Outside of Eclipse I updated two text files in my working
copy, a .java file and a .properties file.
As before, when I open Eclipse to the Resource perspective on my working
copy, the label decorations indicate that my project is up to date.
Neither file is marked as being out of date. But when I run the svn
command line client outside of Eclipse those two files show up as
modified. I have my preferences set to refresh at startup, but just to
be sure I tried F5 and refreshing from the context menu. It sure
appears that the workspace is not being refreshed. Changing to the
JavaSVN interface mode has eliminated my startup errors though. I now
normally get no error messages on startup.
Any other ideas? I've seen references in the eclipse change logs to
refreshing in a background thread. Is there any way to force a
synchronous refresh, to be sure it actually completes?
Thanks,
Bob
Received on Sun Nov 20 07:20:56 2005