Book a Demo

Author Topic: move package under version control  (Read 2979 times)

Graham_Labdon

  • EA User
  • **
  • Posts: 66
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
move package under version control
« on: June 26, 2008, 05:31:54 pm »
Hi All
I have a model with a package structure with each package under source control (I am using Vault from Source Gear).
I now need to move some packages around.
The only way I see of doing this is to disconnect the package from source control and then to re add it in the new location.
This results in losing the source control history.

Is there a better way of doing this ?

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: move package under version control
« Reply #1 on: June 27, 2008, 08:44:52 am »
Check out the original parent package, and the new parent package.  Drag the package between the packages and check in both packages.

Aurelien

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
  • Senior Business Analyst
    • View Profile
Re: move package under version control
« Reply #2 on: June 27, 2008, 05:35:11 pm »
This procedure will allow to move the packages in the EA project browser. But the location of the files in the VC system will not reflect the new structure.
I have the same problem using TFS: I don't know how to safely move packages in the VC repository (eg using visual studio) without losing their history. How to let EA know that the packages have moved no a new place?
A.
A. Slodzian

Frank Horn

  • EA User
  • **
  • Posts: 535
  • Karma: +1/-0
    • View Profile
Re: move package under version control
« Reply #3 on: June 27, 2008, 06:47:24 pm »
Either you delete the packages from EA and reimport them from their new location (Get Package), or you hack the xmi files.

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1214298302

The problem not only arises when you want to reorganise your packages, but also when you want to copy them to a branch or tag in the version control repository. EA offers no banching and tagging, and if you do it with your version control client, the EA models in the new branch or tag will still refer to the xmi files in the trunk.