On Tue, May 27, 2008 at 3:46 AM, Tom Walter <walter.tom_at_gmail.com> wrote:
>
> Mark Phippard wrote:
>>
>> I think it notifies us of "your files" that changed. But for example,
>> when you switch a project every .svn folder in the project gets
>> rewritten to the URL. None of those folders make it to us to refresh
>> unless the switch operation also modifies one of your files in that
>> folder.
>>
>
> Would it be fair to say then that the only files which would change during a
> svn operation would be the ones that svn reports has changed, plus the .svn
> folders in each folder below the folder the svn operation occurred on?
No, it will update all of the .svn folders beneath whatever resource
you selected. If you switch the entire project, it is all folders in
the project. Likewise, we refresh based on the resource you selected.
> If so, could subclipse avoid triggering a full refresh simply by passing
> eclipse the files that svn reported changed, and then a list of .svn folders
> built up by recursing through the folders beneath the one the svn operation
> occurred on?
>
> Sorry to revive an old thread, but this issue causes me considerable
> hassles. I understand that the slowness of the refresh is mostly the fault
> of the plugin I am using for development (PDT), however the need to do a
> full refresh comes from subclipse. If subclipse could work properly without
> requiring a full refresh, it would be good for those who are working with
> other plugins such as PDT which may be slow at building.
Have you considered just turning on the automatic workspace refresh
option in Eclipse?
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-27 17:21:16 CEST