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.
Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 7 17:24:54 2007