| Summary: | Compilation issue when a metamodel in the workspace depend on a metamodel deployed as plug-in | ||
|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Yvan Lussaud <yvan.lussaud> |
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | stephane.begaudeau |
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
I believe this issue is a duplicate of this resolved bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=362985 The problem in the other bug was ultimately an incompatibility between a query defined on EClass on a module using a metamodel depending on Ecore. The module had two ns URI, the one from the metamodel (located in the workspace) depending on Ecore and http://www.eclipse.org/emf/2002/Ecore. So the query taking an EClass as a parameter was using the type http://www.eclipse.org/emf/2002/Ecore#//EClass while the metamodel had a dependency to platform:/plugin/org.eclipse.emf.ecore/model/Ecore.ecore#//EClass. A fix has been contributed on HEAD and R3_2_maintenance, it will be available in Acceleo 3.2.1 and 3.3.0. *** This bug has been marked as a duplicate of bug 362985 *** Closing resolved bugs |
Hi, I have a metamodel located in the generator plug-in (in the workspace). The source code is generated. This metamodel has a dependence to an other metamodel deployed as plug-in. The compiler seems to load two different EClasses for the same EClass : <letVariable name="var"> <eType xsi:type="ecore:EClass" href="http://snipe#//Smurf"/> <initExpression xsi:type="ocl.ecore:PropertyCallExp"> <eType xsi:type="ecore:EClass" href="platform:/plugin/snipe.ecore#//Smurf"/> As a workaround I will deploy the first metamodel. regards, Yvan.