Bug 270730 - Match & Diff engine association using content-type instead of file extension
Summary: Match & Diff engine association using content-type instead of file extension
Status: CLOSED FIXED
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2009-04-01 05:07 EDT by Gonzague Reydet CLA
Modified: 2009-11-23 11:43 EST (History)
1 user (show)

See Also:


Attachments
Patch implementing the engine association within content-type and namespace (112.77 KB, patch)
2009-11-23 11:29 EST, Gonzague Reydet CLA
laurent.goubet: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gonzague Reydet CLA 2009-04-01 05:07:54 EDT
The extension points that enable the contribution of custom match and diff engines only allows the engine to be associated to specific file extensions.
It would be interesting to be able to associate those engines with a content-type or by a namespace instead of file extension. For example this is interesting when several versions of a metamodel are available for a unique kind of model (i.e. models within the same file extension).
Comment 1 Gonzague Reydet CLA 2009-11-23 11:29:58 EST
Created attachment 152873 [details]
Patch implementing the engine association within content-type and namespace

This patch implements the association of match engines, diff engines and diff extensions within a given content type or namespace.

Match and diff engines can also be associated with a namespace pattern.
Comment 2 Laurent Goubet CLA 2009-11-23 11:42:01 EST
Comment on attachment 152873 [details]
Patch implementing the engine association within content-type and namespace

Thanks for your involvment :). This patch has been commited on HEAD.
Comment 3 Laurent Goubet CLA 2009-11-23 11:43:05 EST
Forgot to FIX