Losing Changes in SVN Controlled Model

[davidgsteadman]

Hi,

We're trying to enter user/issue information into a model. The model is split into a number of XML files, checked into SVN.

A different user can checkout all the checked-in changes, but isn't seeing updated user/issue data.

1 - Would I be right in thinking that this is being stored in the EAP file rather than our configured XML files, so the commits aren't allowing the data to be shared?
2 - Even if '1' is/isn't true, what do I need to share this info?

Thanks,
Dave Steadman.

[HowardB]

Hello Dave,

When you apply version control to your model, Package data is exported to XMI files and these are then placed into version control.  Some of the data used in your model, the Reference Data, is not stored as part of any particular package, but it can still be exported to an XML file and subsequently imported into another model.

Currently, EA does not provide an integrated means for version controlling the Reference Data.  Of course it is still possible for users to manually apply version control to these XML files.

From the main-menu, choose "Tools | Export Reference Data..."  then select the tables that you wish to export, such as "Model Authors", "Project Roles", "Project Issues" and click "Export".

To import the reference data into another model (as you would need to do to share this data to another user in a Private Model deployment), choose "Tools | Import Reference Data..." from the main-menu.


Best regards,
Howard Britten

[darren.sampson]

Hi guys,

Another thing to note is that XMI import can lose data, so storing a model in more than 1 XMI file (including using EA's version control) is a bad idea unless:

1) You have no connectors between objects in the different XMI packages
2) You are extremely careful!

If you decide to be extremely careful, some guidelines:

EXPORT:
If you export a package with connectors to objects in another package, you must also export the other package.  There is no indication in EA of these connectors, so it is a bit hard to spot.  At Ripple we developed a tool to detect this.

IMPORT:
When importing a set of XMI files with connectors across the packages into a "clean" model, you must import all XMI files TWICE!!  This is a flaw in EA's XMI Import which throws away any connector when the object in the other package does not yet exist.  Importing twice works around this issue.

Hope that helps!
Darren