Book a Demo

Author Topic: Duplicating large package structure...  (Read 3272 times)

Krzysztof Swiatkowski

  • EA User
  • **
  • Posts: 76
  • Karma: +0/-0
  • Understanding is a three-edged sword
    • View Profile
Duplicating large package structure...
« on: April 15, 2009, 10:46:39 pm »
Hi,

is there a way to copy large package structure in EA without going thrugh XML? Currently I export the tree to xml and import it again with new guids. But it takes ages to process very large xml file back and forth :).

The reason for such action is we are working on new version while the old one is still being worked on. So I need to take current state of the model make a new branch of it inside one repository and allow working on both.

Regards
Kris
If I put you finger in the eye
then you have finger in the eye
and I have finger in the eye
but it's not the same

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Duplicating large package structure...
« Reply #1 on: April 15, 2009, 11:28:29 pm »
Maybe you can try project transfer.
That will copy your whole project to another database.
The good thing about this is that you do not loose your guid's, and you could use the compare/merge facility to merge changes back into the main branch.
There are a few whitepapers on the site of EA that explain some of this stuff.

Krzysztof Swiatkowski

  • EA User
  • **
  • Posts: 76
  • Karma: +0/-0
  • Understanding is a three-edged sword
    • View Profile
Re: Duplicating large package structure...
« Reply #2 on: April 15, 2009, 11:52:54 pm »
I thought about that but unfortunately in worst case scenario there are 4 concurrent versions of the system:
- Current - system the way it works now - no changes
- Tested - system that has been developed and is now being tested - very small changes
- Developed - system that has been analyzed and is undergoing development in dev teams - changes that come from realisation of RQ's both big and small :)
- Analyzed - new system features that are being prepared - frantic changes :D

Right now I'd rather have someone conciously update 1-3 models in single repo than go into somehow automated update.
Also there is a question: does merge work correctly with diagrams? Or just the structure?

Regards
Kris
If I put you finger in the eye
then you have finger in the eye
and I have finger in the eye
but it's not the same