Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use pure ecore models instead of UML #20

Open
GoogleCodeExporter opened this issue Jul 15, 2015 · 0 comments
Open

Use pure ecore models instead of UML #20

GoogleCodeExporter opened this issue Jul 15, 2015 · 0 comments
Labels
auto-migrated Component-Metamodel Maintainability Priority-High Type-Feature-Request

Comments

@GoogleCodeExporter
Copy link 

it would be much more easy to maintain the edapt-integration when the meta 
model would be pure ecore instead of UML. currently, all changes to the UML 
file have to be manually done to the ecore file again to let edapt create the 
history.

I dont know any advantages by the use of UML and I think all extended 
functionality during the UML genmodel extension could be done within ecore 
itself.

is there anything that cannot be done without UML?

Original issue reported on code.google.com by aljoschability on 2 Jul 2012 at 3:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Metamodel Maintainability Priority-High Type-Feature-Request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter