Bug 157617 - [Wizards] 'Change Sharing' should be possible on multiple projects
Summary: [Wizards] 'Change Sharing' should be possible on multiple projects
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-09-18 05:31 EDT by Markus Keller CLA
Modified: 2019-09-06 15:34 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2006-09-18 05:31:53 EDT 
I20060918-0010

'Project context menu > Properties > CVS > Change Sharing...' should be possible on multiple projects. Almost always when I need to change the CVS connection, I need to do it on multiple projects at once.

One way to solve this would be to support opening the CVS Properties page on a multiselection. Another way would be to add 'Change Sharing...' as an action to the Team context menu.

The action should not care too much about the selected projects. A batch change should also be possible when the selected projects use differing (or even incompatible) connections.
Comment 1 Michael Valenta CLA 2006-10-02 13:47:48 EDT 
This is sort of possible today by changing the properties of the repository lcoation in the Repo view. However, this changes the sharing for all projects mapped to the repo. Providing a Change Sharing for multiple projects would require a new UI gesture since the current operation is available on the properties page which is only available for single selection. We do not plan on addressing this for 3.3.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:34:54 EDT 
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.