Book a Demo

Author Topic: Integrating EA w/ third party version control  (Read 3631 times)

Scab

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • Guru wannabe...
    • View Profile
Integrating EA w/ third party version control
« on: August 03, 2006, 12:45:13 pm »
We are in the process of acquiring a third-party version control package. In one of the EA user guides it mentions Microsoft Common Source Code Control standards are necessary to integrate with EA. Can anyone offer a definition of what these standards are and if there is a quick way for us to determine which software packages comply with these standards. Thank you for your any help.

Reference:
http://www.sparxsystems.com.au/EAUserGuide/index.html?versioncontrol.htm
« Last Edit: August 03, 2006, 12:45:37 pm by matt_stallings »
~ Matt

thomaskilian

  • Guest
Re: Integrating EA w/ third party version control
« Reply #1 on: August 04, 2006, 03:48:47 am »
Maybe you tell us the name of your desired product, so someone could answer: works/not. EA works with Visual Source Save (see Microsoft sources) and many other products.

Scab

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • Guru wannabe...
    • View Profile
Re: Integrating EA w/ third party version control
« Reply #2 on: August 04, 2006, 05:42:54 am »
The software package is McCabe CM - if there is a way to determine their compatibility, please let me know

Thanks.
~ Matt

thomaskilian

  • Guest
Re: Integrating EA w/ third party version control
« Reply #3 on: August 06, 2006, 01:41:40 am »
I can't remember of any thread talking about that product :-/ Maybe someone else has???

So to give you a different start: you can set any package to controlled giving an extrernal XML file which then can be controlled via almost any version control. For yourself you could investigate if there is any VSS compatibility mode with McCabe. In that case you could use direct version control inside EA.