Sharing .eap file when using subversion.

[implementer]

Hi,

We're just started running enterprise architect 6.1 Professional and has set up a project containing some packages. All packages are connected to package control via subversion. Checking in and out the packages works fine. But...

The problem is what to do with the project eap file. We haven't come up with a solution for handling it. This file must be writable when working in the project but since it is not a textfile we will use the lock-procedure for editing it. So how can multiple users work at the same time? Is it possible to handle the version control of this file directly from Enterprise Architect?

While trying to solve this our procedure is update the project eap file, make a local copy, remove ready-only and then run it. This is of course everything but smooth...

Is there some fix/solution/tip, or maybe we are heading of in the wrong direction? If so, please guide us back..

[Jan ´Bary´ Glas]

We use DB repository instead .eap for our team work. My best practices are setting need of locking elements you update and than just lock few elements and work. The others can see your changes by refreshing diagrams /reopening elements properties.
Does it help, implementer?