[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.modeling.mdt.uml2] Re: PackageMerge in UML metamodels

Sorry Vlad, but you are on the wrong track ...

Package Merge is a concept defined in UML 2 (Infrastructure 11.9.3). It is used to combine the contents of two packages based on some transformation rules. The UML2 metamodel itself makes heavy use of Package Merge to organize its contents and to define the compliance levels. It has nothing to do with nested packages.

Cheers,
Marco


Vlad Varnica schrieb:
Hi Timothy,

What do you mean by package merge ?
Do you mean to be able to have an UML Superstructure having nested packages ?
Do you mean that project information such a classifier in Package 1 and another classifier in package 2 which can have dependencies need to be saved in the UML Superstructure model ?


I remember that in 2006 we have this discussion inside Omondo and that we had to find a workaround to support nested packages with EMF. I don't remember anymore how it works but if you keep looking you will definitely find the solution. It was a really very long and painful job but we did it because we are toll vendor and this is our job.
If you have no time and a budget to purchase our very very expensive tool then you can try our EclipseUML build for Eclipse 3.4 and 3.5.
You have graphical and UML superstructure nested packages support.


-see graphical reprensentation at:more at: http://www.forum-omondo.com/documentation_eclipseuml_2008/reverse/reverse/nested_package_display.png


- see UML Superstructure at: http://www.forum-omondo.com/documentation_eclipseuml_2008/reverse/reverse/model_has_been_created.png



Sorry to come back to sell Omondo's tools but the package merge is an important point and what I have seen with other open source projects is not what should be done !! I think that this package support is very important. Do not hesitate to send us an email for a quote at sales at omondo.com
Thanks,


Vlad,