Description Alan Langford 2005-02-13 11:58:36 EST

I work on several projects. Some internal, some client-related, and several open
source. Some of these projects share common code in libraries; some live in
their own isolated environments. It is common for many to have their
repositories set up in a very flat way, with each module in it's own directory
off of the root.

Thus the flat project structure in Eclipse causes problems: if two projects on
two different source repositories have conflicting names, then I wind up
applying my own prefixes to the project names (eg. project1_Parser,
project2_Parser, etc.) This still leaves me with a long list of hundreds of
projects that is hard to manage.

The option of creating different workspaces for each client is largely
unworkable. The cost of a context switch and managing settings is too high, and
sharing of common modules between projects is impaired.

It would therefore be highly useful to be able to create project groups, and to
be able to move projects in and out of groups, to check a project out into a
group, and to have the "Close Group" function close all projects in that group.