Share SVN model

[ArnPSA]

Hello,
I have a model under subversion and I want to give it to someone else for him to see how UML works.
My problem is that he doesn't have access to the subversion server (and he won't), so I want to give him a SVN free .EAP How can I do that without configuring each package one by one by hand?

Thank you for your help.

[Paolo F Cantoni]

Start with your .EAP file, check everything out.

then just give him a copy of the EAP file.  It will contain everything.

So long as he doesn't try to check-in he should be able to do everything he wants to "play" with UML.

After you've made his copy, check everything back in from your copy.

HTH,
Paolo

[ArnPSA]

Thanks for your answer, it should do the trick for this time.

Any other "cleaner"/more professional  method to do it ?

[Paul Lotz]

Paolo's suggestion is simple and clean--and the best way to do this.  Just give your .eap file to the person.  (You don't actually have to check everything out first--just make sure your packages are up to date.)  It doesn't get much simpler than that.

[pH]

Export the EA model as XMI and other person can just import it to have really "svn free" model. You can also importxmi and then share the EAP.

thx,
pH

[ArnPSA]

Thanks for your answers.

@Paul Lotz :
If I don't do a check out before sharing my eap the other person can not edit it. So it seems that check out is necessary.

@pH :
When I export my model (or a package) as XMI and then import it in another project it keep it on svn. And this branch is synchronized between the two project (as if it was a pointer to the same xml file).

It seems that check out project and share it is the best solution.
Or maube I missed something.

[Paul Lotz]

"@Paul Lotz :
If I don't do a check out before sharing my eap the other person can not edit it. So it seems that check out is necessary."

Not true.  When the person opens the .eap file you send, EA will try to connect to the version control server, but since this isn't possible, it will open .eap file with the packages not version-controlled (necessarily!).  At this point the person can edit them to his or her heart's content.  Of course, the person won't be able to check in the changes, but then he or she would need version control for that.  Anyway, try it!  

[pH]

I am not sure what you meant by "it keep it on svn".
When you export a model/package, the destination where it gets export by default would be svn location. But that can be changed to any non-svn location on local drives. In such case it will be totally "svn free"

pH

[Geert Bellekens]

Doesn't Project/Work Offline help?

Geert

[ArnPSA]

No if I do Project/work offline, all my packages are still "on SVN" (there is still the little key on all packages) but I can then do a checkOut package by package and work on it. But for a professional use it's not great to say to our clients "you have to manually check out every packages to use our model".

For now the best method is still to do a checkout of all packages and then distribute the .EAP.

NB: It's easier/faster with EA 8 because I can do a checkout in branch wich I couldn't do with previous version.

Thanks for your answers !