Community
Participate
Working Groups
Eclipse provides a facility for configuring working sets, but there is no way to export and/or share working sets with others. It would be helpful if one could import/export working sets from an XML file stored with projects. For example, the file .workingsets in the following directory structure could define the project names and locations of projects in a directory tree. For example: / .workingset projectA/ .project projectB/ .project common-libs/ commonA/ .project commonB/ .project Where the .workingsets document contained XML that grouped projectA and projectB in one working set and commonA and commonB in another working set.
I too would like this feature along the lines of the question I've asked on the eclipse newcomers list. http://www.eclipse.org/newsportal/article.php?id=11518&group=eclipse.newcomer#11518
Tod: you've covered this off right?
Currently we only allow for export between workspaces. Moving back to Kim for general export.
The AnyEdit plugin (http://andrei.gmxhome.de/anyedit/) includes a Working Set export/import wizard. Perhaps the author could be contacted and asked if he would contribute the code...?
I don't know if this request pre-dates the Team Project Set export/import feature, but that includes Working Sets. This should be closed/resolved.
I agree with comment 5, the team project set export is able to export working sets, so this could be marked as fixed.
*** Bug 138854 has been marked as a duplicate of this bug. ***
I did not find a way to export my working set unless all the projects have proper and 100% correct scm data and on import it insists on importing the projects despite I already have them. So yes team project set gets very close to this but has some quirks that makes it not that general usable.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
