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

Bug 86814

Summary:

[Change Sets] 'Compare with .. Date' shows wrong revisions in Synchronize view in Change Set 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:

Keywords:

helpwanted

Version:

3.0.1

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
All seems to work ok	none

Description Markus Keller

2005-02-28 06:23:20 EST

3.0.2RC2 - I200502161722 and also 3.1 - I20050222-0821:

I had jdt.core from HEAD in my workspace and did a 'Compare With > Another
Branch or Version...' . I added a date from one day ago and pressed OK.

Now, when the Synchronize view is set to show Commit Sets (3.0.2) / Change Sets
(3.1), the revision from HEAD is taken for both versions (expected: one is the
HEAD revision, the other one is from the chosen date). This makes the
Synchronize view unusable since it
- displays wrong labels (e.g. JavaCore.java - ...   1.443 - 1.443)
- on double-click, opens a compare editor which compares the HEAD revision with
itself (empty change)

Comment 1 Michael Valenta

2005-03-30 09:27:52 EST

We wont have time to address this in 3.1

Comment 2 Krzysztof Daniel

2007-02-07 10:46:57 EST

Created attachment 58447 [details]
All seems to work ok

I have eclipse 3.3M4 and cannot reproduce described behavior.

When I set the date one day ago I receive 'no changes found' message (correct behaviour).

When I modify the code and then compare with 'yesterday', I receive comparison of two files with the same tag (eg 1.4) but one is set as Local, the other as Remote.

Comment 3 Eclipse Webmaster

2019-09-06 16:15:28 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-12 10:49:20 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.