We have been using eGit for a long time without problems.
But recently, a big project was moved from SVN to Git, and it is causing some performance problems with eGit (4.0.0 in Mars, Windows 7).
The project has 3600 java files in 25 projects, taking some 5 minutes to compile.
When I switch to a new branch, it looks like all java files are recompiled (individually, or batched, I don't know).
So this takes around 5 minutes.
But this recompilation takes place in the context of the old branch.
The new branch may have other dependencies, and these are not updated until the Workspace refresh completes, and the project builders are invoked.
We use Gradle for this, so project settings are changed, causing another full build.
I wonder if the JDT incremental builder can be disabled while eGit makes changes to the workspace?
Or is something else at play?
If I disable Build Automatically, the branch switch will take the same amount of time.
And files will be processed via org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged.
Thanks,
Jesper Skov
Digitale Medarbejdere
|
T +45 89 89 29 89
Vestergade 8-16 | 8600 Silkeborg
CVR-nr. 17 61 66 17
Jyske Mobilbank med
Swipp - send penge nemt og hurtigt
|
![]()
![]()
|
|
![]()
|
