Summary: | Support Workspace Description Files | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Martin Oberhuber <mober.at+eclipse> |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | cdtdoug, daniel_megert, lj, mn, mschorn.eclipse, Szymon.Brandys |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Martin Oberhuber
2008-08-27 11:57:52 EDT
As additional constraints, the following features would be interesting: * Importing an EWS file into an existing workspace should override/merge the settings. That way, a team administrator could roll out workspace level changes to the entire team easily. Similar functionality is requested by bug 198569. * The EWS file should be in a user-readable (and editable) format. That way, team members can review the changes being rolled into their workspace before applying an admin-provided change. Drag & drop of an EWS file into an existing Eclipse workspace would be a nice metaphor for rolling in updated settings (that were obtained by E-Mail for instance). If the roll-in / merge functionality works well, a concept like P2 "watched folder" could also be applied: In the Team environment, the workspace is configured to watch URL x for updates to the workspace. Only admins have write permission into URL x, and can use that URL for rolling out updates to workspace team settings. Watched URL x could also reside inside the workspace, such that team synchronization of the workspace itself would trigger an update of settings. *** Bug 198569 has been marked as a duplicate of this bug. *** Good to see you raised this bug Martin. Unfortunately it's been five years. But I think this problem becomes more prevalent with git. And I just ran into this, I did a Pull to get the latest master and we have a huge number of plug-ins. But we don't import them all into our workspaces. We have some that are pretty dead and don't even build any more. Well someone added a new plug-in and it was hard to find. Importing the projects gives you almost an all or nothing feel. Team Project Sets could be the answer but ideally, when you did the git pull, the new projects should get imported automatically. That's where a workspace description file would come in very handy. So +1 from me. I'm dying to get back into this issue and flexible resources in general, so may be able to help out if I get a chance. |