I am working on a large, multi-module Maven-based system, with approximately 20 submodules and an additional small number of external dependencies between projects, which are also Maven projects in my Eclipse workspace. In total, there are about 30 projects in the Eclipse workspace.
Projects are all imported maven projects with m2e, and we use Subversion (with the Subversive plugin) for version control. Eclipse is the recently updated Kepler.
My workstation is fully functional, with a 4-core Intel i7 processor, 16 GB of RAM and a solid state drive.
The problem is that Eclipse is very slow when it comes to:
Team synchronization and conflict resolution. Every time I correct the conflict and "Mark as merged", I have to wait 10-30 seconds for Eclipse to update the workspace, etc. Not to mention the fact that the conflict conflict tree is then cleared completely, so I need to choose the outbound mode, then for refilling. Twice - because it is cleared when I save the resolved source file, and then again when I mark it as merged.
Building. I am using the Maven launch configuration to build Maven. But for some reason, making a Maven build is not enough for Eclipse - it must also build its own build of the entire workspace, which takes at least the same amount and much longer, when Eclipse decides to hang for a few minutes on "Cleaning the project xxx project output folder", for several projects.
The result of all this is that it often takes more than an hour to update from the original control, resolve conflicts, build, and prepare to launch or continue development.
My colleagues and I often think that Eclipse hinders development when it should strengthen it.
Is there anything that can be done to reduce the eternal expectation syndrome-Eclipse?