Community
Participate
Working Groups
Currently, the Sirius tools work only with the original ecore and genmodel resource types. Xcore has been promoted as a newer representation for EMF models, and offers significant advantages, such as method body generation and the use of Xbase. It's possible to generate ecore and genmodel files from xcore models, but the results are not ideal for reasons I won't go into here (I owe Ed Merks a bug report on this topic). Bottom line, with direct support for xcore in the Sirius tools, they aren't worth the trouble for xcore users. Since many members of the community are now using xcore, the Sirius tools should work with them directly, so that we can all benefit for the Sirius features.
I'm marking this bug as a blocker from an xcore user's perspective. Please feel free to change the priority, since it's not a blocker from an ecore user's perspective.
Hi Jack and thanks for your feedback. There are so many things which can be assumed by "support XCore" that we definitely need more information. If I'm not mistaken, an Xcore metamodel will register the EPackage just like an Ecore model, hence should work at runtime with Sirius. But no specific support has been done for Xcore meaning right now you don't get any code completion in the .odesign file for typenames for instance. Or maybe it is something else you expect which is not working ? Could you please describe what exactly "does not work at all" for an Xcore user and what would be your expectations ? Please do so with steps we could reproduce quite easily.
I'm reducing the severity until we have feedback on what are the concrete issues at hand.
Jack, I'm closing this for lack of actionable details. Feel free to reopen if you has concrete use cases that do not work as expected.
