| Summary: | EMFCompare does not work with resources that use content types | ||
|---|---|---|---|
| Product: | [Modeling] EMFCompare | Reporter: | John Conlon <jconlon> |
| Component: | Core | Assignee: | EMF Compare <emf.compare-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jconlon, laurent.goubet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
John Conlon
This is (or at least, was) due to Platform/Compare only considering the very first content type it finds when searching for comparison viewers; we have no way to influence this. However, IIRC, they added a drop-down list to allow users to switch from one viewer to the other (Text to EMF in your case) and back on the compare editor that opens up.
For the time being, you can try and bind your own content types to EMF Compare's viewers (note that if you do, registering your extension in the preference for EMF Compare is no longer needed) :
<extension point="org.eclipse.compare.contentMergeViewers">
<contentTypeBinding
contentMergeViewerId="org.eclipse.emf.compare.ui.contentmergeviewer.ModelContentMergeViewer"
contentTypeId="my.content.type.id"/>
</extension>
<extension point="org.eclipse.compare.structureMergeViewers">
<contentTypeBinding
structureMergeViewerId="org.eclipse.emf.compare.ui.structuremergeviewer.ModelStructureMergeViewer"
contentTypeId="my.content.type.id"/>
</extension>
Closing as wontfix as we cannot do any more to influence this. |