Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 164144

Summary:	[Change Sets] Model-based Synchronize view with change sets shows incoming set in outgoing mode
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	172027

Description Markus Keller

2006-11-10 12:36:17 EST

I20061108-1600

See scenario and screenshot (attachment 53639 [details]) in bug 164142. The model-based Synchronize view shows change sets and is in outgoing mode. Still, an incoming change set is shown: "[maeschli] (10.11.2006 ...".

Incoming mode is correct. Incoming/outgoing mode and conflicts mode show both change sets.

Works fine in non-model-based synchronizations (there, incoming/outgoing and conflicts mode do not show change sets).

Comment 1 Markus Keller

2006-11-13 05:01:38 EST

In outgoing mode, I selected QuickFixProcessor.java in "my outgoing change set" and chose context menu > Update. The outgoing change set disappeared, but the (wrong) incoming change stayed (showing QuickFixProcessor.java 1.79 - 1.79).
When I switched to incoming mode and then back to outgoing mode, the wrong entry disappeared.

Comment 2 Michael Valenta

2006-11-15 13:20:35 EST

Unfortunately, we don;t have the manpower to address change set related issues in 3.3.

Comment 3 Eclipse Webmaster

2019-09-06 15:32:19 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.

Comment 4 Eclipse Genie

2021-10-25 05:11:49 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.