Author Topic: Using XML files with CVS  (Read 3638 times)

jvs

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Using XML files with CVS
« on: September 17, 2003, 06:53:35 am »
I would like to put my EA models under CVS source
control.  The problem is the eap files are binary and
hence do not work well with CVS, which prefers text
files.  CVS would copy the entire .eap file upon each
checkin.

It seems like exporting the diagrams to XML and then
putting the XML files under CVS would be the way to
go.  I would have to ask developers to always import
from the XML file rather than working on their .eap files
in order to get the latest version.

My questions:
1. Is anyone else successfully doing this?
2. Is there a better way to integrate CVS with EA?
3. It seems like it would be best to export the entire
   view rather than individual diagrams as that would
   be the only way to retain the complete structure.

Any comments or answers would be welcome.

Jim VS


Sean Kearon

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Re: Using XML files with CVS
« Reply #1 on: September 17, 2003, 08:51:09 am »
Hi Jim

We are intending to do a similar thing as we have a couple of seperate models which we will want to merge into a master model.  

I think that you will need to export a whole self-consistent package, or set of packages, for this to work.  (EA does not allow you export just the diagrams, you need the the package which they sit in.)

If a diagram in a package contains an element from another package, then the other package must exist in the model to which you are importing or the element will be lost from the diagram.

Sean

Phil_Bachmann

  • EA User
  • **
  • Posts: 38
  • Karma: +0/-0
    • View Profile
Re: Using XML files with CVS
« Reply #2 on: September 17, 2003, 04:19:24 pm »
The latest version of EA has an interface to SCC-compliant Source Code Control systems including CVS bridges like Igloo and Tortoise.

Phil Bachmann
Sparx Systems