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

Re: [Subclipse-users] Synchronize view - individual files not showing?

From: Eric Berry <elberry_at_gmail.com>
Date: 2007-09-07 18:16:53 CEST

   Please correct me if I'm wrong, I'm a basic user of the products, but
doesn't Subversion version the folders as well. So if you commit your files
from the synch view, then go to incoming changes, you technically should see
the folders, because each of their revisions need to be updated. Whenever I
commit my files, I always have to go to the incoming changes to update the
revisions on the folders, and I don't see the files I just committed.

This might explain the issue where Jay isn't seeing his own committed files
and only seeing the folders, but wouldn't help in the case where another
colleague had made commits.

Jay, are you perchance doing updates outside of the synch view?


On 9/7/07, Mark Phippard <markphip@gmail.com> wrote:
> On 9/7/07, Jay Levitt <lists-subclipse@shopwatch.org> wrote:
> > Mark Phippard wrote:
> > > On 9/7/07, Jay Levitt <lists-subclipse@shopwatch.org> wrote:
> > >>> That is a feature. It is described here:
> > >>>
> > >>>
> http://markphip.blogspot.com/2006/12/subclipse-synchronize-feature-show-out.html
> > >> I do understand "show outdated folders", and I can see how this might
> be
> > >> related - but it's (at least slightly) a separate issue, because this
> > >> occurs whether I have that enabled or disabled.
> > >
> > > I am still convinced it is only because of this feature. One thing
> > > about this feature is that it does not toggle on/off very easily. The
> > > issue is that the feature effects the information that gets into our
> > > cache, and once info is in the cache it will stick there. In your
> > > case, if you turned the feature off, and then updated everything it
> > > would likely stay off.
> >
> > I don't mean to be difficult, but I don't see how cached out-of-date
> > folders could result in the changed files being -missing- from the
> > changeset. I could see how otherwise-unchanged folders would still show
> > up, but under those folders (or maybe under an identical-looking but
> > genuine folder node) I'd expect to see the changed files that really do
> > need updating. That's the bug I'm concerned about.
> >
> > Is there a way for me to blow away the cache? If not, could you point
> > me toward some interesting points in Subclipse I could step through to
> > debug? I have some time this weekend.
> I'd love to have you or anyone try to make Subclipse better.
> Unfortunately, the Synch view is probably not the place to start. One
> of the reasons I am talking around this issue is that even if you file
> a bug, I am not going to look at it. I can never make heads or tails
> of how that view works because the Eclipse API is just so complicated
> and involves so much cache. We have had some other committers that
> come back for short periods that seem to grok this better and have
> made most of the improvements over the years.
> I am going based on my own observations using the view and what I see
> in similar situations. I have not had situations where files go
> missing, other than the known problem where toggling the view mode
> seems to resolve it.
> As for the cache issue, I was more answering the other points you had
> made which I think are explained by the cache. The missing files I do
> not have an explanation for. I just have not experienced that myself.
> --
> Thanks
> Mark Phippard
> http://markphip.blogspot.com/
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org

Learn from the past. Live in the present. Plan for the future.
Received on Fri Sep 7 18:13:34 2007

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.