Best way to share a package

[ngong]

Assume 2 or more models sharing a set of basic data types in a certain package.
It has been xmi exported by the front-most project and imported by others at starttime.
All projects refer to the same GUID when they refer to a certain datatype.

Now assume the front-most model extends that basic types package, corrects some flaws and improves some of the types.
What would be the best strategy to get those changes to the other model as well?

[qwerty]

The most simple would be either as controlled package (which allows manual save/load as XMI) or as VC package (which is almost the same but allows to use a version control system). It depends on your use case which you prefer. If a VC is present, using that would probably be the best choice. It's advisable to enable user locks and lock the package in question to some administrator. That prevents usual modelers from (accidentally) modifying that static asset.

q.

[Uffe]

Hello,

I know I bang on about this but the best way to do this is to use the reusable asset service -- the use case you describe is pretty much specifically what the RAS was designed to address.

It's not the simplest, but it is the best. It allows you to check differences, has a level of access control so you can restrict who can update the centralized models, and tracks dependencies between assets.

/Uffe

[Eve]

I'd say that best depends on your needs, but other than that I agree with Uffe and would recommend RAS.