Eclipse Community Forums: EMF » Import of Ecore model without regenerating ecore model code

Help

Home

Home » Modeling » EMF » Import of Ecore model without regenerating ecore model code

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

Import of Ecore model without regenerating ecore model code [message #1351915]

Tue, 13 May 2014 08:08

Jens P.

Messages: 2
Registered: May 2014

Junior Member

Hi there,

I'm struggling with a problem when importing Ecore models into different projects.
I have a set of plug-ins, which each has its own Ecore model but are included in the same Eclipse app. Some of these models are dependent of others and include them via a simple line of code in the .emf file.

Example: deploy.emf

import "platform:/resource/com.example.resource/model/resource.ecore";

Everytime I generate the the deploy.emf code the code from the resource project will be recreated again in the deployment project. So as I start the Eclipse application both projects (Resource and Deploy) try to register the the resource package which results in a ClassCastException. I intend to transform the models via Eclipse ETL, so I assume, that there is no distinct single class that could be used by the application.

Is there something nicer than this import command? Perhaps something that is closer to a "reference"? I tried to avoid exporting the code for an imported package by altering the MANIFEST.MF file but it just gets overwritten by the EuGenia processes.

Thanks a lot for quick answers or advices, I really need them.

Jens

Report message to a moderator

Re: Import of Ecore model without regenerating ecore model code [message #1352539 is a reply to message #1351915]

Tue, 13 May 2014 14:08

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Jens,

Comments below.

On 13/05/2014 2:57 PM, Jens P. wrote:
> Hi there,
>
> I'm struggling with a problem when importing Ecore models into
> different projects.
> I have a set of plug-ins, which each has its own Ecore model but are
> included in the same Eclipse app. Some of these models are dependent
> of others and include them via a simple line of code in the .emf file.
Note that mutually dependent models need a single GenModel and must be
generated into a single project...
>
> Example: deploy.emf
>
> import "platform:/resource/com.example.resource/model/resource.ecore";
>
>
> Everytime I generate the the deploy.emf code the code from the
> resource project will be recreated again in the deployment project.
I can't really comment on how EuGenia works, so it's best to ask about
that on the eclipse.epsilon forum. With a "standard" EMF GenModel,
you'd specified a dependency on another model via a usedGenPackage so
that you reuse the already generated code and don't generate a copy of
it locally...
> So as I start the Eclipse application both projects (Resource and
> Deploy) try to register the the resource package which results in a
> ClassCastException. I intend to transform the models via Eclipse ETL,
> so I assume, that there is no distinct single class that could be used
> by the application.
>
> Is there something nicer than this import command? Perhaps something
> that is closer to a "reference"? I tried to avoid exporting the code
> for an imported package by altering the MANIFEST.MF file but it just
> gets overwritten by the EuGenia processes.
>
>
> Thanks a lot for quick answers or advices, I really need them.
>
> Jens

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator