Since this topic has come up several times I added an example
workspace configuration to:
http://wiki.eclipse.org/index.php/Mylar_User_Guide#Workspace_setup
Others should feel free to add their own recommendations to this.
Mik
Mik Kersten wrote:
Since your workspace needs seem roughly similar to mine, here's a
quick summary of how mine is set up:
* Over 100 Java and plug-in projects checked out from CVS and SVN
repositories, some of these projects are huge.
* 6 working sets that define project/product boundaries (e.g. Mylar,
Tasktop). Thanks to working sets I only work in one Eclipse workspace.
* Package Explorer and other navigator views set to have their
top-level elements be working sets.
* Problems list set to show only working sets that I contribute to
(on those projects there is a policy of no warnings, and I like to
keep this view empty).
* To keep things like text search matches reasonable I usually have
my search scopes look through only the projects I contribute to.
For keeping my workspace focused on task I obviously use Mylar's
focused mode on the navigator views, and as a result I almost never
open and close projects. Since Eclipse's indexing and search
facilities work eagerly and on-demand, and Mylar keeps the number of
my editors from bloating, I do not notice any noticeable performance
degradation even with my large workspace. Auto building is the same,
once one full build has run, the JDT's incremental compiler means
that making a change to one source file should not take noticeably
longer no matter how many projects you have checked out.
Let me know if you have further questions. I suggest trying to set
up your working sets, and then letting the tools do their job and
complaining when they don't or when your see any appreciable
performance degradation.
Mik