|Re: Best Practice for teamwork with papyrus [message #1223495 is a reply to message #1223063]
||Mon, 23 December 2013 15:08
| Camille Letavernier
Registered: February 2011
There are currently three ways for team working with Papyrus. Two of them are still experimental (In development), and the last one is developed outside the Papyrus project, so I can't tell much about it.
The first one, easiest to set up, is using Git + EMF Compare. Git provides the versioning system, and EMF Compare the compare viewer and mergers for models (Including tree and diagram views; Tables are currently not supported). As the EMF Compare/Papyrus integration is still under active development, it might be interesting to use the versions shipped with Luna M4 (Or to wait until Kepler SR2, in February 2014).
The second one, which requires a little bit of configuration and deployment, uses CDO (Connected Data Objects). CDO relies on databases to store models. As for EMF Compare, the CDO integration in Papyrus is still under development. I haven't tried the latest releases, so I'm not sure which features are available so far. I think versionning is not available yet.
The last one is ModelBus, which provides a connector for Papyrus, as well as team capabilities. I cannot tell much about this component, because it is not part of the Papyrus project, and I haven't really tried it.
Powered by FUDForum
. Page generated in 0.02081 seconds