Bug 157180 - [Sync View] Synchronize view not always in synch with package explorer view
Summary: [Sync View] Synchronize view not always in synch with package explorer view
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-13 11:23 EDT by Olivier Thomann CLA
Modified: 2019-09-06 15:34 EDT (History)
0 users

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 Olivier Thomann CLA 2006-09-13 11:23:40 EDT 
Using I20060912-0800, I noticed that sometimes I can still see error markers on the resources in the synchronize view when they have already been fixed.
The package explorer view is clear from error markers.
If I make an aditional change and trigger a build, the error markers in the synchronize view are removed.
I am almost sure that this used to work in 3.2.
Comment 1 Bogdan Gheorghe CLA 2006-09-13 11:31:36 EDT 
Olivier demoed this for me using the latest I build - so it is happening ;) - but I haven't been able yet to reproduce this on my machine...
Comment 2 Olivier Thomann CLA 2007-03-19 13:27:38 EDT 
It still happen with I20070313-1051.
It remains always one build behind. Like I need an extra change (like remove/add a whitespace) and recompile to get the error decorators removed from the synch view.
Comment 3 Michael Valenta CLA 2007-05-04 11:53:35 EDT 
I suspect this is an update problem in the Java synchronization label provider since the updates work properly in change set mode. Unfortunately, I didn't have time to look into it for 3.3.
Comment 4 Szymon Brandys CLA 2008-05-09 04:23:52 EDT 
Mass update - removing 3.4 target. This was one of the bugs marked for
investigation (and potential fixing) in 3.4 but we ran out of time. Please ping
on the bug if fixing it would be really important for 3.4, and does not require
API changes or feature work.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:34:58 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.