Bug 69659 - [Actions] Selecting multiple folders invalidates team options
Summary: [Actions] Selecting multiple folders invalidates team options
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, usability
Depends on:
Blocks:
 
Reported: 2004-07-08 15:07 EDT by MG CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MG CLA 2004-07-08 15:07:00 EDT
If you select a set of folders where one or more folders isn't under revision
control, the team update option is greyed out.  This should not be the case.  

If you selected a parent folder and check the team menu it will not be greyed
out.  Sometimes it is necessary due to cvs bugs - like resource already exists -
to select a set of folders instead of the parent and do an update.  Having to
unselect folders that are not under revision control is a pain.
Comment 1 Michael Valenta CLA 2004-07-14 11:02:46 EDT
A better approach is to fix Eclipse so it keeps going when such a situation
occurs (see bug 62327)
Comment 2 MG CLA 2004-07-14 13:33:34 EDT
True cvs shouldn't bomb out on an error that is an annoying bug as well but the
point of this bug is that you can't activate an update from the team menu - the
option is greyed out - if you have selected a set of folders in the navigator
where one of the folders is not under revision control.  Even if you fix cvs
such that it doesn't bomb out I am not sure how that fixes the UI to not be
greyed out where you have selected a folder not under revision control.  
Comment 3 Jean-Michel Lemieux CLA 2004-08-31 08:42:04 EDT
I'm not sure what the UI guideline is for action enablement based with multi
select. We decided to disable an action if any element in the selection was not
applicable.
Comment 4 Al Stone CLA 2006-01-14 19:32:15 EST
The same problem occurs on Linux. of course.  Even just trying to update the Eclipse platform source from CVS, I cannot select several of the CVS projects (com.eclipse.*, for example) and update them; and, to work on the platform, it seems you have to have a lot of projects.

If I create a patch, is there any chance it will be accepted into upstream?
Comment 5 Michael Valenta CLA 2006-01-15 20:07:14 EST
Yes, patches will be accepted. 
Comment 6 Al Stone CLA 2006-01-30 11:52:52 EST
My bad.  Now that I understand this better, I will contend this is *not* a bug, but is indeed how eclipse should behave.  What I _thought_ I had run into is that I could not select multiple CVS projects, and use the team menu to update them all at the same time; that would have been a bug if eclipse did not handle it -- but it handles it quite well.  The situation originally reported is different from what I thought it was -- a non-CVS project is in the midst of a multi-select region that contains some CVS projects, and that in turn disables the team CVS functions.  While it would be nice if there were some sort of indication that this had happened, it _does_ make sense for eclipse to behave this way.  So, my apologies for the noise, but I now think that the behavior as originally reported is actually the correct behavior and would even recommend closing this bug.
Comment 7 MG CLA 2006-01-30 13:12:32 EST
I still think this is a bug.  The description is not for multiple project selection this is multiple folder selection within a project.  

A good use case is that inside your one project you want to update everything exception the build folder, so you open the project select everything except the build folder then do team and find update is disabled.  You are then required to deselect any folder or items that are not updatable.
Comment 8 Eclipse Webmaster CLA 2019-09-06 16:14:38 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.