Re: Performance: why rebuild even if no change after update?
Have you trues to add .svn/** to the build path excludes? That should
help to not build when only svn files had been changed.
Marc Guillemot wrote:
> Thanks for the explainations.
> Are there some plans to improve performance or does it have only a low
> Martin Letenay wrote:
>>> after an update that hasn't retrieved any file (because the project
>>> is already uptodate), it seems to me that Eclipse starts to re-build
>>> the whole project. Wouldn't it make sense that subclipse inform
>>> Eclipse more precisely about which files have been changed?
>> Yes. It would.
>> Well, it's know problem but there's not know 100% correct solution.
>> The very problem comes from the subversion itself.
>> Even in case there was no change done to the working copy, the (AFAIR)
>> .entries file in .svn meta folder is touched on the filesystem.
>> Subclipse then, does not parse the content of the .entries, but just
>> on the "resource modified" event reported by the underlying eclipse ...
>> There are few more such less-than-optimal features of Subclipse
>> related to
>> The main problem is to find out reliable mechanism for various events
>> - to
>> watch for modification to files done within eclipse (edits), to check
>> for modification caused by svn actions triggered by subclipse and also to
>> recognize the changes done to working copy by external tools (cmd line,
>> tortoise etc ...)
>> And of course not forgetting the reather poor performance of "svn
>> status" on
>> Windows' filesystems
Received on Tue Oct 11 17:02:21 2005
This is an archived mail posted to the Subclipse Users