RE: [Subclipse-users] RE: Subclipse "Switch" very slow compared to "svn switch"

Alexander Kitaev wrote:

> Hello Irvin,
>
> I could be wrong, but as far as understand Subclipse performs
> full project refresh after merge and switch operations.

Oh, I see. Is there any reason why it needs to be this way?
Most of the time when I perform a switch for my project, very few files
will have actually changed
(and in this example, 0 files had actually changed).

> ...
> If your project is out of sync with the filesystem it could take
> some time, also refresh may cause full project rebuild.

For this example, I had a completely up-to-date project, and then
performed the switch.
Nothing was actually updated as part of the switch, so Im confused as to
why the eclipse project would need to be built from scratch.

Id appreciate any further insights very much :o)

> Alexander Kitaev,
> TMate Software,
> http://tmate.org/
> http://jetbrains.com/tmate/
>

Dave Irving

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Apr 10 14:08:58 2006