[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [Subclipse-dev] Post merge refresh.

From: Alexander Kitaev <alex_at_tmate.org>
Date: 2006-03-28 20:49:28 CEST

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 changed
if there is no corresponding merge event).

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 update?

> 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 python
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 have
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 personally
suffer from it, and would like to help in making post-merge refresh more
optimal.

Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/

> -----Original Message-----
> From: Mark Phippard [mailto:markp@softlanding.com]
> Sent: Tuesday, March 28, 2006 20:30
> To: dev@subclipse.tigris.org
> Subject: RE: [Subclipse-dev] Post merge refresh.
>
> "Alexander Kitaev" <alex@tmate.org> wrote on 03/28/2006 01:25:29 PM:
>
> > Hello Mark,
> >
> > > I added this to Switch and Merge because there were scenarios,
> > > probably depending on what WC changes were made by the
> action, where
> > > things just did not refresh correctly and the decorators were not
> > > updated.
> > May be modifications made could be analyzed and only when such
> > scenario
> is
> > matched, root resource should be refreshed and otherwise only those
> > resources that were affected by merge?
>
> 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.
>
> > > Technically it refreshes the resource you selected when
> you took the
> > > option. I realize in most cases this means the whole project.
> > Yes, that how it works for me - I'm merging a single file and then
> > wait
> for
> > several minutes for the whole project to be refreshed.
>
> When I have done it, if my project is in synch the Refresh
> always ran fast.
>
> Mark
>
>
> ______________________________________________________________
> _______________
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe
> Plc by IBM Email Security Management Services powered by MessageLabs.
> ______________________________________________________________
> _______________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Tue Mar 28 20:50:29 2006

This is an archived mail posted to the Subclipse Dev mailing list.