Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341716 - Text Compare - No extension mechanism in TextMergeViewer to ignore case in DocLineComparator
Summary: Text Compare - No extension mechanism in TextMergeViewer to ignore case in Do...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-03 06:36 EDT by Tobias Melcher CLA
Modified: 2019-11-27 07:17 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Melcher CLA 2011-04-03 06:36:40 EDT
Build Identifier: I20100608-0911

Hello colleagues,

we would like to use the eclipse compare framework to show diffs for ABAP sources. To reduce the amount of diffs, case for keywords should be ignored. Unfortunately, the TextMergeViewer class doesn't provide an extension mechanism or callback method to overload the compare detection logic. Method TextMergeViewer#doDiff delegates to DocumentMerger#doDiff and DocLineComparator instances are created for left,right and ancestor. We would like to use our own DocLineComparator implementation which is case insensitiv for keywords.

Would it be possible the extend the compare framework and provide either an extension point or a method which can be overloaded to realize our use case?

With best regards,
Tobias Melcher

Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-27 07:17:37 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.