Bug 204550 - Unnecessary processing of other projects in synchronize perspective during updated
Summary: Unnecessary processing of other projects in synchronize perspective during up...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-25 10:06 EDT by Ken Larson CLA
Modified: 2019-09-06 16:05 EDT (History)
1 user (show)

See Also:


Attachments
Screenshot (234.58 KB, image/png)
2007-09-25 10:08 EDT, Ken Larson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Larson CLA 2007-09-25 10:06:25 EDT
Build ID: I20070625-1500

Steps To Reproduce:
1.Synchronize a workspace with multiple projects, where only 1 project has changes on the server
2.In the synchronize perspective, only the changed project is visible
3.Click to update
If you have enough projects, you'll see the names of many other projects in the dialog.


More information:
This is scary because it implies that it is updating projects that you did not ask it to.

It does not in fact do anything wrong, it merely leads you to believe that it is.
Comment 1 Ken Larson CLA 2007-09-25 10:08:14 EDT
Created attachment 79129 [details]
Screenshot

Observe how in the screenshot there is only 1 project with incoming changes.  However, the dialog shows that it is processing "ffmpeg-java", another project in my workspace, which I would not update if it had shown changes.
Comment 2 Szymon Brandys CLA 2007-10-01 04:56:04 EDT
Build id: I20070625-1500
I can observe this too.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:05:05 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.