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

RE: [Subclipse-users] Refresh issue when using "switch"

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-11-09 22:22:33 CET

"MATHUS Baptiste" <mathus.b@mipih.fr> wrote on 11/09/2006 06:50:37 AM:

> +1. I think I encountered this problem recently too :-/. The thing I
> it a little bit late, and so I disconnected, then shared the project to
> commit a completely new version of the fucked up working copy. I do not
> if it's subclipse fault at all, but maybe subclipe should call a refresh
> the project root after a switch ?
> Should we log an issue for that or aren't you able to reproduce this
behaviour ?

Sure. I actually took the refresh out in 1.1.8 because I thought that a
change made in JavaSVN was going to make it unneccesary. I am a bit
surprised that some of the problems stated could happen, because I would
not think a value in our cache could even remotely possibly effect the SVN
API's and what they do. We do not tell SVN where to commit, it knows from
the WC.

Putting back the refresh is a 1-liner though.


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Nov 9 22:22:40 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.