Enable/Disable "Refresh SVN status cache" #48
Comments
|
I have modifies 5 files in the subclipse.core and subclipse.ui projects to add this functionality ;) Cheers, |
|
I have a very similar probelm and a quick test of your solution worked well. |
selsemore
added a commit
that referenced
this issue
Jan 17, 2019
Add a new 'Ignore refresh SVN status cache' preference. If true, the 'Refresh SVN status cache' job does not get executed when workspace file changes are made. This is a patch from the changes.zip file that marcgise provided in the issue. I've just rebased it and also moved the 'ignore refresh' check down to just before the status cache refresh job would be scheduled. That way the auto sharing of SVN projects will still occur. Issue #48
|
We merged a version of this option to add a preference and will include it in the 4.3 release. Hopefully it will help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a process that modifies a lot of files in the Workspace. The problem is that each time a file is modified, a background Job named "Refresh SVN status cache" is executed, and it slow down my process drastically.
It would be great if there exists a preference that allows to enable/disable this Job. This way, previously to execute my process, I disable the Job, and once ended, I enable it again.
I consider it necessary, as it is reducing a lot my productivity.
I found that the file that starts the Job, is org.tigris.subversion.subclipse.core.resourcesListeners.FileModificationManager.
Some approach like the one for derived resources, maybe is valid to solve this issue.
The text was updated successfully, but these errors were encountered: