如果这些项目完全独立，我将创建单独的工作空间，每个工作区一连串的项目，不能独立建造。是否有一个原因您不想拆分到多个工作区？我很确定这是Eclipse在这种情况下的用途。我已经做了很多次，发现它是一个很好的解决方案。

When you have 5+ languages and 100+ projects, IMO the default of using one workspace is not acceptable because the one workspace becomes horribly disorganized. Having one huge unorganized workspace lowers your productivity.

The question:

What are the more advanced ways of using Eclipse when you have 5+ languages and 100+ projects? I would really appreciate advice that elaborates a little bit more than just giving one sentence like "use multiple workspaces" or "use working sets".

"Must have" requirements:

• The project navigator only shows related projects (like only projects from abc language or only projects from xyz language)
• The described method is currently being used by you or someone you know and has been used for more than two weeks

"Would like" requirements:

• the ability to be able to have projects with the same name (like "helloworld" for language xyz and "helloworld" for language abc)

(Side note:

FYI, one of the reasons for asking on SO.com is because I have searched enough on Google to know that there are LOTS of people who have the same "Help my Eclipse workspace is out of control" problem. )

If these projects are completely independent from each other, I would create separate workspaces, one workspace for each set of projects that are connected and cannot be built on their own. Is there a reason you don't want to split to multiple workspaces? I'm pretty sure this is how Eclipse was intended to be used in this case. I've done it many times and find it to be a good solution.