EA Deployment

[Maggie]

Hello
I have been the sole developer of a model under version control.
Now I have a colleague who needs to access the same repository.

Do we need to share an eap file? - I tried putting the eap file on a shared network drive but we cannot both have this file open.

What recommendations does anybody have about the best approach to take

Thanks for your time

Maggie

[qwerty]

Export the root as EAB under VC
Your colleague imports the model branch into an empty local EAP
Via VC you both share the same model locking packages during changes.

There's a white paper on Sparx site detailing that.

q.

[Geert Bellekens]

Or use a proper database.
Seems a little strange though, I always thought eap files could be accessed by multiple people at the same time (since they are MS Access databases, so limited multi-user should be possible-

Geert

[Oliver F.]

Sharing the same instance of the EAP file is outlined by Sparx in the deployment whitepaper so it ought to be working.
If not other constraints might apply coming from your infrastructure (eg. a file system lock).

For version control operation there is no need to share EAP files. These are only used as local repostiories in which you check out the model so I would be pretty careful trying to share this to prevent inconsistencies and confusion.
The standard approach is every single user of the CVS keeps his own EA file which is filled from version control.
This is also outlined in the version control whitepaper provided by Sparx.

Best regards,

Oliver

[Maggie]

Thanks to everyone