Bug 28202 - contentmergeviewers do not work with mixed-case extensions
Summary: contentmergeviewers do not work with mixed-case extensions
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-12 13:51 EST by Rolf Wilms CLA
Modified: 2003-02-03 04:54 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 Rolf Wilms CLA 2002-12-12 13:51:59 EST
When a contentmergeviewer is registered for a certain file extension via the 
extension point, this contentmergeviewer will not work if the extensions of the 
actual files do not match in capitalization.

Example: 
t1.properties compare with t2.properties opens PropertyMergeViewer
t1.properties compare with t2.PROPERTIES opens default TextMergeViewer
t1.PROPERTIES compare with t2.PROPERTIES opens PropertyMergeViewer

Even registering the extension in both lower and upper case in the extension 
point does not help.

I think a contentmergeviewer should be used if
a) regardless of the capitalization of the actual file extension
b) if any of the file extensions registered with the extension point match for 
any of the files to be compared
Comment 1 Andre Weinand CLA 2003-02-03 04:54:15 EST
fixed for M5