Bug 290231 - Incorrect enablement of the "Update All" button
Summary: Incorrect enablement of the "Update All" button
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2009-09-23 05:48 EDT by Igor Burilo CLA
Modified: 2019-09-06 16:14 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 Igor Burilo CLA 2009-09-23 05:48:19 EDT 
In Synchronize View in toolbar Update All button (or 'Update All Incoming Changes...' button in CVS) becomes enabled even if no incoming changes available. For example just after pressing the "Populate" link.
Steps to reproduce:
1. Make synchronize, project doesn't have any changes
2. restart Eclipse and open Synchronize view
3. As you can see Update All button is already enabled
3. Click Populate link, there are no changes but Update All button is enabled

Build id: 20090619-0625
Comment 1 Tomasz Zarna CLA 2009-09-28 08:08:46 EDT 
Repeated the same steps on I20090922-0800 for a CVS synchronization.

(In reply to comment #0)
> Steps to reproduce:
> 1. Make synchronize, project doesn't have any changes
> 2. restart Eclipse and open Synchronize view
> 3. As you can see Update All button is already enabled

Confirmed, this is wrong.

> 4. Click Populate link, there are no changes but Update All button is enabled

Clicking either "Populate" or "Synchronize" result in disabling the button when no incoming changes are found. This seems to be working for me.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:14:57 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.