Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: paulinjm on September 30, 2004, 12:00:22 pm

Title: Sharing an EAP file
Post by: paulinjm on September 30, 2004, 12:00:22 pm

Does anyone have experience with sharing an EAP file (same project - two people)?  We have been having some issues.

Thanks
Jason

Title: Re: Sharing an EAP file
Post by: Row on October 01, 2004, 01:01:28 am

We have been sharing an .eap file and it works fine. We have enabled security though and made everything locked unless you unlock it.
We are three persons working activly with that file.
What issues did you have?

/Robert

Title: Re: Sharing an EAP file
Post by: paulinjm on October 01, 2004, 01:17:27 pm

At times things don't show up from one computer to the other and then other times when we close the application and reopen it, there is alot of garbage on some of the screens we worked on.  Not sure what is causing it.

Jason

Title: Re: Sharing an EAP file
Post by: Martin Terreni on October 03, 2004, 12:12:00 am

hi Paul

I have a couple of teams doing team-work with EA and (eccept of macking trouble with vertion control) all works fine. maybe you should try using replication and keeping a master file for team making every one work an private replication, then merging -it works fine.

Title: Re: Sharing an EAP file
Post by: Row on October 04, 2004, 07:45:40 am

We work with user locks. Before applying a user lock, you need to reload the project, so you know that current diagram is the latest version of that diagram. Reload a project is done from the File menu (reload current project).
It sounds like you guys are working towards the same diagram simultaniously and to my knowledge that doesn't work.
The garbage I can't explain, I have not seen that.

/Robert

Title: Re: Sharing an EAP file - package control
Post by: mikewhit on October 06, 2004, 01:17:37 am

Although I have been having issues using (Corporate) EA and version control with a database repository, it might be that using version controlled packages to share a non-database EA model would provide the benefits you require.

You can use a Microsoft-supported version control like Source Safe, or CVS (I have used Jalindi Igloo to interface EA to CVS).

Having set up v.c. on the project, you then specify that the  packages are 'controlled packages' and put them into v.c.

This means that only one user can update a package at once, although all other packages are readable.

This may give you enough of what you require, together with the benefits of a central controlled repository.

However, EA does not readily support loading an earlier version of model files, so if you ever have to go back for any reason, you'll have the files there in CVS, but you'll have to access them 'manually'.

The EA Help and user guide files are good on setting up Version and Package control, but not so clear on actually using it and completely silent on backtracking a model, though to be fair this might be down to Igloo's shortcoming.

There is also an Igloo mode [Package Control - Start Version Control Explorer] setting - Auto Commit , Regular CVS or Work Offline that you should decide on.

Mike

Title: Re: Sharing an EAP file
Post by: paulinjm on October 06, 2004, 06:55:08 am

Thanks for everyone's suggestions :)