Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Modeling (top-level project) » Different output model directories for interfaces, impls, etc?
Different output model directories for interfaces, impls, etc? [message #654454] Tue, 15 February 2011 20:56 Go to next message
Kelvin Lim is currently offline Kelvin Lim
Messages: 1
Registered: February 2011
Junior Member
Hi all,

What's the easiest way to have different types of model classes go to different output directories?

My team has structured our workspace so that interfaces, implementations, and factories reside in different Eclipse projects. However, as far as I can tell, a EMF genmodel only allows us to specify a single model directory for all its output.

Right now, we're manually moving the output classes to different projects, but this is cumbersome and makes it harder to take advantage of the built-in merge capability.

Any pointers at all would be most appreciated. I'm new to EMF, so apologies if this is a basic question!

Thanks,


KL

Re: Different output model directories for interfaces, impls, etc? [message #654525 is a reply to message #654454] Wed, 16 February 2011 08:11 Go to previous messageGo to next message
Vincent MAHE is currently offline Vincent MAHE
Messages: 129
Registered: July 2009
Senior Member
Le 15/02/2011 21:56, k@kelvinlim.com a écrit :
> Hi all,
>
> What's the easiest way to have different types of model classes go to
> different output directories?
>
> My team has structured our workspace so that interfaces,
> implementations, and factories reside in different Eclipse projects.
> However, as far as I can tell, a EMF genmodel only allows us to specify
> a single model directory for all its output.
>
> Right now, we're manually moving the output classes to different
> projects, but this is cumbersome and makes it harder to take advantage
> of the built-in merge capability.
>
> Any pointers at all would be most appreciated. I'm new to EMF, so
> apologies if this is a basic question!
>
Hum! The use of interfaces, factories,... in EMF generator is more a
questions of design patterns than a high level architecture. The
generated code in all corresponds to the Ecore metamodel, which is a
single homogeneous artefact. As this, it should remains in one Eclipse
plug-in (at, least, it makes sense to split editor and model parts).

Your structure seems to target other constraints or goals. May be you
should adapt your way to do things to the tools you use for that...
--
Cordialement

Vincent MAHÉ

Ingénieur Expert - Projet IDM++ - Équipe AtlanMod
École des Mines de Nantes
La Chantrerie - 4, rue Alfred Kastler
B.P. 20722 - F-44307 NANTES Cedex 3
Tel: (33)2 51 85 81 00
Re: Different output model directories for interfaces, impls, etc? [message #654546 is a reply to message #654525] Wed, 16 February 2011 08:53 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26014
Registered: July 2009
Senior Member
Yes. In fact the factory interface refers to the default implementation
class via its eINSTANCE...


Vincent MAHE wrote:
> Le 15/02/2011 21:56, k@kelvinlim.com a écrit :
>> Hi all,
>>
>> What's the easiest way to have different types of model classes go to
>> different output directories?
>>
>> My team has structured our workspace so that interfaces,
>> implementations, and factories reside in different Eclipse projects.
>> However, as far as I can tell, a EMF genmodel only allows us to specify
>> a single model directory for all its output.
>>
>> Right now, we're manually moving the output classes to different
>> projects, but this is cumbersome and makes it harder to take advantage
>> of the built-in merge capability.
>>
>> Any pointers at all would be most appreciated. I'm new to EMF, so
>> apologies if this is a basic question!
>>
> Hum! The use of interfaces, factories,... in EMF generator is more a
> questions of design patterns than a high level architecture. The
> generated code in all corresponds to the Ecore metamodel, which is a
> single homogeneous artefact. As this, it should remains in one Eclipse
> plug-in (at, least, it makes sense to split editor and model parts).
>
> Your structure seems to target other constraints or goals. May be you
> should adapt your way to do things to the tools you use for that...
Previous Topic:[EMF] "@generated NOT" does not work
Next Topic:Best tools for new Java XML SQL app
Goto Forum:
  


Current Time: Tue Sep 02 21:36:01 GMT 2014

Powered by FUDForum. Page generated in 0.03677 seconds