Book a Demo

Author Topic: Versioning attachments  (Read 2979 times)

Sandeep

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Versioning attachments
« on: December 07, 2007, 08:20:53 am »
I am trying to figure out a way to ensure that attachments within my model (Functional Technical Requirements) can be versioned like the models. The attachments can be word or excel files for example.

I am using CVS for versioning.

Any ideas?

Thanks

thomaskilian

  • Guest
Re: Versioning attachments
« Reply #1 on: December 07, 2007, 11:51:50 am »
Write an add-in to export that stuff to files. Then VC these files using Tortoise.

Amol

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Versioning attachments
« Reply #2 on: December 07, 2007, 01:41:25 pm »
Somewhat related to the original question -

How can we attach any type of file within an EA project file? My requirement is that such files be embedded within the .eap file, and not as a link to another location.

I want the .eap file & the attached files to be recognized by the same version. My guess is if I maintain them seperately in CVS, I would also need to maintain a mapping betwen project and attached file versions.


thomaskilian

  • Guest
Re: Versioning attachments
« Reply #3 on: December 08, 2007, 01:39:53 am »
I simply created a directory structure similar to EA's and VCed that. Usually that works without problems. The root contains the controlled packages and where necessary I create appropriate sub-folders.