How to get referenced packages via Version Control

[ch]

Hi,
I have a problem with linked objects in packages which are version controlled. I have two packages A and B. Package B consists of linked objects of package A.
When I now load package B into another model via "Package Control" but not package A, the linked objects aren't displayed, of course. Is there a possibility to ask the version control to load also referenced packages or at least to get a warning that there are linked objects from other packages.
The problem is, if a user doesn't know the reference and saves the model without to include the referenced package, the linked objects are deleted.

Thanks in advance!

[ChrisDr]

Hi,

this is a problem that, to my knowledge, has been  addressed to Sparx several times. Other programs solve this by stubs (eg. Rhapsody). Currently this is *THE* major issue here for a bigger roll-out.

To my knowledge no other solution exists than do a "Get All Latest" before any check-out (which can be quite time consuming and requires some discipline). I'm currently thinking of developing an AddIn that at least notifies me about possible information loss but I'm not far yet.

@Sparx: PLEASE ADDRESS THIS ISSUE!!! It's a major concern especially for larger installations/bigger teams.

Chris

[Geert Bellekens]

Please report this issues using the official channel (bug report or feature request links on the bottom of the page)
This is a user forum, so Sparx people may not even notice this topic, and they will definitely not take action based on it.

Geert

[ChrisBD]

The only way around this that I have seen is to have cross package references by instance rather than simple link.
Ideally you should have an interface types defined high up in the model that will be used to attach to a given package. Then any package that uses them can use an instance reference rather than a simple link to use them.
That way you don't have this problem.
Think of a package as a DLL and you'll see what I mean.