Weird behaviour with nested version control

[D. Miller]

Hello all,

We are currently using EA 7.1 and TFS for our version control. Also we have mixture of SQL Server and EAP repositories.

The weird behaviour I am experiencing occurs when I check out a root package.  Under the root package I have number of child packages for my separate Domain Managers and inside these packages I hold my sequence diagrams and interface classes.

When I check out the root package, objects are lost from my diagrams in version controlled child packages. I can even watch them being deleted from the t_object table on the database.  

If I do a 'Get Latest' on the affected child package the objects (in this case Fragments) re-appear.  Also If I do a 'Get Latest' on a separate package, under the same root, the position of the objects in the diagram move.

Does anyone know what is causing this? Does EA not fully support nested Version Control?

Thanks

[Eve]

It is normal for elements inside a package being checked out to be deleted from the t_object table.  Any XMI import deletes the package and then re-imports it.  But this information should all be restored during the import.

At one point, and I'm not sure about the current behavior, if you had classes from another package directly on a sequence diagram the connectors between them could get lost.  The recommendation at the time was to use instances of the class instead of the actual class.

If you still have concerns, please contact sparx support directly.

[2stefant]

We hade similar problems using Perforce for version control and nested controlled packages gave us a lot of trouble, especially the root.

Our solution was to skip version control and use only the shared db and let our server (hourly backup) be our lifeguard.

We enabled user security, use locking but do not require user to do it.

Also the import function is dangerous - Why is the "Strip GUIDs" checkbox not checked by default? When importing the same data twice by mistake it actually trashed our diagrams elsewhere in the model. The warning says "data will be overwritten in the current package".

Steve