Fair enough. Odd that subversion wouldn't notify for every file it
changed... that is something that would be a worry even working with the
command line.
Mark Phippard wrote:
> On Mon, May 5, 2008 at 4:08 AM, Tom Walter <tom.walter_at_hitwise.com> wrote:
>
>> I've been experimenting a little, and it does seem to be the refresh
>> process which is slow. A refresh of the full project after updating the
>> directories using the svn command line client takes a similar length of
>> time.
>>
>> Would subclipse be able to speed this up by only instructing eclipse to
>> refresh the files it knows were changed as a result of an
>> update/switch/merge? Presumably a switch shouldn't require eclipse to
>> rebuild the entire project?
>>
>
> We already do this for every file we receive Subversion notifications
> for and had the same thought as you. See release 1.1.8. User's
> quickly ran into problems like:
>
> http://subclipse.tigris.org/issues/show_bug.cgi?id=579
>
> And so we put it back. The problem is that Subversion modifies some
> files that it does not send notifications for, and so we cannot know
> to update them. The full refresh is the only answer we know of to
> work reliably.
>
>
Received on 2008-05-06 01:44:52 CEST