|
| Re: One genmodel vs. multiple genmodels [message #501473 is a reply to message #501380] |
Wed, 02 December 2009 13:56  |
 Ed Merks
Messages: 33136
Registered: July 2009 |
Senior Member |
|
|
Pete,
Comments below.
Pete Ellis wrote:
> Hello everyone,
>
> A question that I've been curious about for a while...
>
> Given a plug-in with several packages, each package containing EMF annotated
> model code, I have a choice in how to proceed with respect to generating the
> code:
>
> 1) Build a single genmodel for the plug-in that governs all .ecore models
> and provides a centralized point for all of the plug-ins code generation,
>
> 2) Build several genmodels, one for each package in the plug-in (one-to-one
> association between genmodel and ecore model), or
>
> 3) Build a few genmodels that have some non-overlapping relationship with
> the various ecore models.
>
> In general, are there any advantages/disadvantages to having one vs.
> multiple genmodels in a plug-in containing multiple packages with model
> code? Any reason to choose one over the other?
>
It seems better to have a single one per project, otherwise it's
possible they specify conflicting properties for stuff like the plugin ID.
> Thanks for any insight on this,
> -Pete
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02042 seconds
] 
Search
Help
Register
Login
Home
