Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » Edapt

Help

Home

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » Edapt - Diff-based metamodel migration

Show: Today's Messages :: Show Polls :: Message Navigator

Edapt - Diff-based metamodel migration [message #1702158]

Mon, 20 July 2015 11:58

Brad Schneider

Messages: 4
Registered: July 2015

Junior Member

I have read (cannot find the source atm) that Edapt is able to create a metamodel migration from some sort of diff-based input. Is this true? If so, does anyone have any documentation on how this can be done?

It looks like the documentation on Edapt is fairly limited at this point to a tutorial on using the defined operations via the operations browser to manipulate and record the history of a metamodel. This is useful, and seems to be the main use case intended for Edapt, but much of our modeling is actually done in external tools which generate the Ecore file for us, which breaks that workflow.

Report message to a moderator

Re: Edapt - Diff-based metamodel migration [message #1702229 is a reply to message #1702158]

Mon, 20 July 2015 19:04

Maximilian Koegel

Messages: 253
Registered: July 2009

Senior Member

Hi Brad,

this feature has existed before EMFCompare was updated to a new API, see
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=417343
Due to limited resources we removed the feature for the current Edapt
versions since we will need to implement some changes to support the
current EMFCompare API. The feature you are looking for was implemented
in the ConvergenceView.
Re-enabling it is probably a matter of 2 days of work. A contribution or
sponsored development would help to get the feature readded! ;)

Cheers,
Maximilian

Am 20.07.2015 um 14:51 schrieb Brad Schneider:
> I have read (cannot find the source atm) that Edapt is able to create a
> metamodel migration from some sort of diff-based input. Is this true? If
> so, does anyone have any documentation on how this can be done?
> It looks like the documentation on Edapt is fairly limited at this point
> to a tutorial on using the defined operations via the operations browser
> to manipulate and record the history of a metamodel. This is useful,
> and seems to be the main use case intended for Edapt, but much of our
> modeling is actually done in external tools which generate the Ecore
> file for us, which breaks that workflow.
>
>

--
Maximilian Koegel

Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/

Report message to a moderator

Previous Topic:	[EEF] How to integrate custom widget generator in Component editor
Next Topic:	Server throws exception that it is unable to resolve class

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jul 05 11:09:59 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter