Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334871 - [UML Compare] Use {o.e.e.c}diff.extension extension point to customize ModelStructureMergeViewer
Summary: [UML Compare] Use {o.e.e.c}diff.extension extension point to customize ModelS...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tatiana Fesenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 330183
  Show dependency tree
 
Reported: 2011-01-20 05:57 EST by Tatiana Fesenko CLA
Modified: 2011-04-07 10:06 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tatiana Fesenko CLA 2011-01-20 05:57:16 EST 
Now PapyrusDiffEngine is used to properly process stereotype applications and changes in tagged-values.
EMF Compare provides {o.e.e.c}diff.extension extension point which allows us
1) to postprocess result of DefaultDiffEngine
2) Introduce custom elements for StereotypeChange and TaggedValueChange in DiffModel. This allows us to customize look of the tree (labels and icons) not to mention that it will increase readability of the code.
Comment 1 Tatiana Fesenko CLA 2011-01-20 05:58:29 EST 
Initial version of UML Diff Extention metamodel is committed to org.eclipse.papyrus.compare plugin
Comment 2 Tatiana Fesenko CLA 2011-01-20 05:59:26 EST 
(In reply to comment #0)
> 1) to postprocess result of DefaultDiffEngine
Initial version is submitted
Comment 3 Tatiana Fesenko CLA 2011-01-20 06:04:22 EST 
(In reply to comment #1)
> Initial version of UML Diff Extention metamodel is committed to
> org.eclipse.papyrus.compare plugin
Please customize icons and labels of the elements.
In fact, they can be customized in two ways:
1) using standard EMF Edit providers 
 - this approach is standard, it won't be influenced by changes in the core DiffExtension, but it will need generation of new classes, thus increasing amout of code
2) Override AbstractDiffExtension#getText() and #getLabel() methods. 

I'd prefer to use approach (2) as it is less standard, but more lightweight.
Comment 4 Tatiana Fesenko CLA 2011-02-10 04:45:53 EST 
Fixed in r3840