[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.modeling.mdt.uml2] Re: Operations Package Export in GenModel

This isn't a bug so much as design intent, from the perspective that operations classes are meant to be "internal" to the implementation of the metamodel. I suppose that specialized metamodels (e.g. for those that extend UML) might want/need to reuse operation implementations, but I don't know how often that would happen. In any case, I'm not sure this change can be made in a maintenance release since it effectively changes the "API" of the model plug-in...

Kenn

James Bruck wrote:
Hi John,

This does seem like a bug. Please raise a defect on UML2 and possibly contribute a patch if you have one.
This could possibly be a candidate for the maintenance release.


Cheers,
- James.

"John T.E. Timm" <johntimm@xxxxxxxxxx> wrote in message news:321b6d7c3f8041ac23eb451481ec4d97$1@xxxxxxxxxxxxxxxxxx
I ended up customizing the manifest.mfjet template to get the required behavior. This does appear to be a shortcoming of the current implemention. If I create a model that uses operations packages and then another model which extends the first, I will get code that doesn't compile until the manifest file is manually updated.

JT

John T.E. Timm wrote:

Is there a way to specify in the GenModel that the Operations Package should get exported so that it can be used by other projects that further specialize the model and also use an Operations Package? I am currently adding an entry to the manifest.mf file manually.
Thanks,
JT
NOTE: I originally posted this message in eclipse.model.mdt, but feel that perhaps the UML2 newsgroup is more appropriate.