Bug 196147 - [Algorithm] Text compare viewer splits insertion into two changes
Summary: [Algorithm] Text compare viewer splits insertion into two changes
Status: RESOLVED DUPLICATE of bug 210688
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2007-07-11 08:56 EDT by Markus Keller CLA
Modified: 2007-11-23 08:46 EST (History)
1 user (show)

See Also:


Attachments
CopyOfSuperTypeConstraintsCreator.txt (4.26 KB, text/plain)
2007-07-11 08:56 EDT, Markus Keller CLA
no flags Details
SuperTypeConstraintsCreator.txt (3.36 KB, text/plain)
2007-07-11 08:57 EDT, Markus Keller CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2007-07-11 08:56:05 EDT
3.3 and I20070710-1416, was OK in 3.2.2

There are situations where the text compare viewer splits insertions into two changes. I'll attach two .txt files which show the difference.

In 3.2.2 and before, the added method endVisit(EnhancedForStatement) in CopyOfSuperTypeConstraintsCreator.txt was shown as a single insertion (good).
In 3.3, the insertion is shown as two separate insertions (rather hard to read).

This is not a Java compare problem (although the stripped-down example files contain Java code).
Comment 1 Markus Keller CLA 2007-07-11 08:56:57 EDT
Created attachment 73529 [details]
CopyOfSuperTypeConstraintsCreator.txt
Comment 2 Markus Keller CLA 2007-07-11 08:57:39 EDT
Created attachment 73530 [details]
SuperTypeConstraintsCreator.txt
Comment 3 Michael Valenta CLA 2007-08-09 16:37:41 EDT
This could be a feature of the new compare algorithm.
Comment 4 Markus Keller CLA 2007-11-23 06:00:47 EST
Hooray, the fix for bug 210688 also resolves this problem.
Comment 5 Michael Valenta CLA 2007-11-23 08:46:23 EST

*** This bug has been marked as a duplicate of bug 210688 ***