Book a Demo

Author Topic: Version Control  (Read 3922 times)

Datron

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Version Control
« on: November 19, 2007, 05:57:38 am »
Hello,

I am new to EA and am experimenting with the version control. It works like it should but I still have a question.
Even if I put the root package "Model" under version control there remains a project file with the extension .eap of about 2 MB. I asume that the project file contains useful information, so should I put it under version control too?
Thanks for your comments.

Regards
Chris
Christian

thomaskilian

  • Guest
Re: Version Control
« Reply #1 on: November 19, 2007, 07:06:23 am »
Simply this is the (MS Access) database where EA is doing the SQL stuff (which is not really feasible with XML).

Datron

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Version Control
« Reply #2 on: November 19, 2007, 08:12:14 am »
That means that if I lose the eap file I'm not able to restore the complete project from the xml file. Hence I have to check in the eap file too... right?
Christian

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: Version Control
« Reply #3 on: November 19, 2007, 07:49:10 pm »
Version control in EA is only for packages.

Other data (reference data) are not version controlled. You can export them and version control on your own.

I think if you export every package and all reference data still something remains and that's the project (I don't know).
« Last Edit: November 19, 2007, 07:49:50 pm by peter.zrnko »
Peter

Datron

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Version Control
« Reply #4 on: November 19, 2007, 11:32:10 pm »
Thanks for your help!

Regards
Chris
Christian