Bug 301793

Summary:	[Sync View] Additions disappear from the sync when reopening a project
Product:	[Eclipse Project] Platform	Reporter:	Tomasz Zarna <tomasz.zarna>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Tomasz Zarna

2010-02-04 04:45:58 EST

I20100202-0800

Steps to reproduce:
1. Prepare a patch with changes and additions
2. Synchronize with the patch
3. Close the project being patched (e.g. in Package Explorer)
=> Sync view shows conflict for the project (good)
4. Open the project
=> Patch is reapplied, changes are there but additions are gone!

This may be related to bug 300215.

Comment 1 Tomasz Zarna

2010-02-16 06:48:06 EST

If in bug 300215 we decide to be consistent and do not display closed project this will be no longer an issue.

Comment 2 Tomasz Zarna

2010-03-04 10:52:00 EST

I'm afraid that comment 1 is not true, but I also noticed that synchronizing with a CVS repo gives the same result. So more general steps look like this:

1. Find a project which you know has incoming additions
2. Synchronize the project
3. Close the project (e.g. in Package Explorer)
=> The project disappears from the Sync view (expected) 
4. Open the project
=> The project reappears but incoming additions do not show up. Other changes are displayed fine. Re-synching with the "Synchronize..." button doesn't change a thing.

Given the fact it's not a bug in applying patches via sync view I'm resetting the assignee, target milestone and removing it from the list of bugs blocking bug 236169.

Comment 3 Eclipse Webmaster

2019-09-06 16:06:48 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.