diff options
| author | Thomas Wolf | 2018-07-02 11:06:22 +0000 |
|---|---|---|
| committer | Thomas Wolf | 2018-07-02 12:10:42 +0000 |
| commit | a8f3b251792dc203433db89300c744c55c8ab4b0 (patch) | |
| tree | 12adbee98dea39a092c8780b558a7ceff64082f9 /org.eclipse.egit.mylyn.ui | |
| parent | 44d6b4988e57a7534b6a0f2115fd00483acf3c63 (diff) | |
| download | egit-a8f3b251792dc203433db89300c744c55c8ab4b0.tar.gz egit-a8f3b251792dc203433db89300c744c55c8ab4b0.tar.xz egit-a8f3b251792dc203433db89300c744c55c8ab4b0.zip | |
Do not refresh projects that use a PessimisticResourceRuleFactory
With some setups where the Eclipse workspace is inside the git
working tree EGit may end up trying to refresh a project that
needs the workspace root as scheduling rule for a refresh. EGit
generally uses multi-rules containing affected projects, though,
and thus it may run into an IAE in that case.
EGit-managed projects use an optimistic rule factory that uses the
project itself as scheduling rule. So do normal unshared projects.
So this can only occur if there are projects inside the git working
tree that are not shared with EGit but with some other provider that
does not use an optimistic rule factory. This is a rare occurrence,
and such projects had better be git-ignored, too. Not refreshing such
projects is a thus viable approach.
Bug: 536472
Change-Id: I17c06fd69e232a7b864a98c4e95598fa7ab6b7b0
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>
Diffstat (limited to 'org.eclipse.egit.mylyn.ui')
0 files changed, 0 insertions, 0 deletions