Updating package with orher project package

[kepNCI]

Given:
- Export Package from Proj A to XML
- Import XML Package into Proj B
- Make updates to package in Prog B
- Export package from Proj B to XML

I now want to import the package back into Proj A, effectively updating the package with the changes made while in Proj B.
EA will not allow me to import it back, since it already exists. Appears only choice is to either:
1) Delete package in Proj A and the import the XML
or
2) Import the XML, stripping the GUID

In either case I loose all links/associations to elements in other packages of the project.
Is there a way to copy a package from a project to another, make updates, move package with updates back into initial pacage while keeping all links and associations?


In case you wonder what I am really trying to do...
I had created data models for all of our production databases via EA re-engineing in an EAP project. I then exported/imported the data models to a SQL server project that is not connected to our production network.  The SQL Server project is a large repository project that not only contains data models, but also has packages that document the production applications, physical devices, enterprise/network topologies, etc.
The data models on the repository are linked to other packages as well as in virtual document definitions. In addition the tables and fields have many notes entered thus enabling a more detailed data dictionary.
It has been several months since the models were re-engineered. I now want to go back to the production EAP project and do another re-engineer so that I can capture any changes. So I exported the data model packages from the SQL Server Repository project and imported them into an eap project located on prpoduciton. I then re-engineered all of the data models. Now I need to take these updated data models and effectivly update the models on SQL Server repository project.

The only way I can think to do it is to transfer the entire SQL server project to an EAP file (DBMS to EAP). Copy the eap file onto the production enviroment. Perform the re-engineering. Copy the eap file back to the supporting enviroments and transer the EAP file back to the SQL Server Repossitory (EAP to DBMS).  I think this would preserve the GUID and this the links/associations.  I was hoping to somehow only work with the Data Model package.
    

[Geert Bellekens]

Hi kepNCi,

What you need is the version control feature in EA (with or without a connection to an external VC system)

See http://www.sparxsystems.com/enterprise_architect_user_guide/9.3/projects_and_teams/versioncontrol.html

Geert

[kepNCI]

Geert
Thanks so much. Never donned on me to look at version control, but it makes perfect sense.  I started to read up on it and one of the first things it states is that you must have a third party version control system.  So, I am interested in your comment that sounds like you can use version control without a third party package. Anything special you must do in the setup?

Karl

[philchudley]

In addition to Geert's suggestion of version control, also have a look at Baselining

Export / Import as per your post
After modeling in Proj B, take a baseline of the imported package
Open Proj A
At the package select Manage Baselines
Load baseline from other eap
Point to project B
You should see Proj B's baseline
Merge Baselines - you get a visual indication of what has changed with options to merge individual items or the complete baseline

Check it out

Cheers

Phil

[kepNCI]

Phil:

Thanks. Definately am going in that direction.

As I read more about versioning, I think that Geert and you are thinking alike, that is, as I currently understand, baselining and compare is EA's internal way of versioning without the use of a third party.

Plan on playing with that today.

Thanks agian, both Phil and Geert

Karl