Book a Demo

Author Topic: Project synchronization with version control  (Read 2770 times)

willdarby

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Project synchronization with version control
« on: October 22, 2007, 03:50:35 pm »
I am trying to understand EA's model for maintaining synchronization between .eap project files and source controlled XMI packages. To illustrate my question I'll present a brief scenario.

1 - Create a project with a model and a view with several sub-packages. Separately version control the model, view and sub-packages. Checkin all elements and save the model.

2 - Checkout one of the sub-packages and add a diagram to it. Save the changes, but do not checkin the XMI sub-package.

3 - A second user opens the shared .eap file on a network drive. That user has a view with the read-only XMI files checked into source control.

4 - The second user does a checkout of the view that contains the sub-packages.

What we observed was that after step 3 the package checked out by the first user was not visible to the second - the entire sub-package appeared to be missing from the model. After step 4 EA seemed to reimport the XMI file and inserted the missing package.

So I have 2 questions:
A - When does EA re-read the XMI file? Upon checkin? checkout? uncheckout? I don't understand why the view was refreshed by performing a checkout.

B - From the basic description above, is there anything obvious that we are wrong in managing .EAP files using the XMI for version control.

Ideas and suggestions are greatly appreciated.

We are using EA 7.0 build 816.

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: Project synchronization with version control
« Reply #1 on: October 22, 2007, 10:59:38 pm »
I'm not going to answer your question. I just want to draw your attention to this setting in Version Control Settings:
  • - saved nested version controlled packages into stubs only[/b]

    EA behavior in situations like you have tested depends on this setting. Is it true or false in your project?



    All version control software (SCC, SVN, TFS, ...) is obviously used in such way, that checkouted files are not shared.
    EA project could be shared and version controlled at the same time. To understand this process takes a "little time". :)
Peter

thomaskilian

  • Guest
Re: Project synchronization with version control
« Reply #2 on: October 23, 2007, 05:46:21 am »
AFAIK EA re-reads after Check-out and on Get Latest. Put Latest writes the current DB contents to XMI and checks it in. Else see Peter's response (especially the last remark).

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: Project synchronization with version control
« Reply #3 on: October 23, 2007, 07:03:21 pm »
Quote
EA project could be shared and version controlled at the same time.


To say it strictly:
EA project could be shared and it's packages could be version controlled at the same time.
Peter