"Alexander Kitaev" <email@example.com> wrote on 03/28/2006 01:49:28 PM:
> Hello Mark,
> > I do not think we have ever found a good explanation for why
> > or when it happens. For example, if you do an update on a
> > Project using the JavaSVN adapter, the last changed revision
> > of the Project does not get refreshed unless you use the
> > Refresh option manually. I have never been able to figure
> > out why that is.
> I do not think this is the case for the merge - merge operation doesn't
> change existing "entries" file, only those in the working copy. Ok, it
> changes entries files when schedules file for deletion or addition of
> course. So, you're saying that when JavaSVN changes such a file Eclipse
> doesn't get notification on that and file status doesn't get refreshed
> automatically? In case of merge all changes in "entries" files should be
> also available as events from SVNClient (i.e. entries files are not
> if there is no corresponding merge event).
The merge/switch issues had nothing to do with JavaSVN. Basically
sometimes you would run the action and the decorators would all be
refreshed, and sometimes they were not.
> Anyway I would like to understand why eclipse doesn't refreshes its file
> cache. Am I understand the situation correctly:
> 1. entries file contents is changed (during update operation).
> 2. Eclipse should fire notification on that, but it does not and
> svnClient.info(...) is not called to get new file or directory revision?
> How eclipse should know that "entries" file contents has been changed?
> Shouldn't refresh be called on project/.svn directory anyway after
We had an email exchange about this once a month or so ago. I think when
you used JavaHL there were a few items coming through as modified that
were not coming through when using JavaSVN. I assume that one of these
items was the reason that the item is not refreshed.
> > When I have done it, if my project is in synch the Refresh
> > always ran fast.
> My project contains non-synched files mostly all the time (because
> tests suite creates its data inside the project, and there are a lot of
> small files). May be this is not usual case, but in general users may
> part of the project in unsychronized state and refreshing whole project
> after console view shows modifications for one or two files could look
> strange for the user. I'm not saying it is a serious bug, but I
> suffer from it, and would like to help in making post-merge refresh more
That would explain the performance difference at least.
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 Tue Mar 28 20:54:07 2006