Community
Participate
Working Groups
Some large customers have workspaces containing several hundred projects. Scoped builds (added in 3.0) were a step in the right direction towards making these workable. Eclipse needs to provide appropriate support for large workspaces and working sets, and ensure that everything scales properly. [Platform Core; Platform UI]
Shouldn't this be in the Resources inbox?
The following document provides a more concrete set of proposed changes that fall under the "large-scale workspaces" banner: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/3.1/large_scale_issues.html
Sharing Working Sets (bug 30687) would also be an important contribution to scalability: Big systems (with many projects) are often logically grouped. Working Sets are a nice way to maintain and visualize this grouping. However, every developer has to define the grouping manually in his workspace, because working sets cannot be shared currently. I would add set operations on working sets (union, intersection, difference), or simple nesting: see also bug 37032 and bug 37389. This could be also helpful for defining and managing sets of projects that have to be build (bug 60803).
Big users of working sets may be interested in the experimental working set browsing capability in the package explorer in 3.1 M4. Feedback on this is welcome in bug 78701. As a work-around, working sets can be shared by copying the file workspace/.metadata/.plugins/org.eclipse.ui.workbench/workingsets.xml between workspaces. Clearly this isn't a strong sharing solution, but I thought it was worth mentioning.
Work on this plan item is completed for 3.1. Refer to the document in comment #2 for details on the work that was done. The main area where little work was done is in the area of better working set support; a follow-on item may be added to the 3.2 plan for work in this area.
