Damus et Capimus

Last week, I introduced the in-progress integration of CDO model repositories into Papyrus for the Kepler release. The starting point was migration of existing models from the Eclipse workspace into a repository. But, what if you don't have models, yet? Do you have to create them in the workspace first, then suck them into a repository?

Not any more!

The latest development on the cdo_kepler branch in Papyrus SVN has refactored the New Papyrus Model wizard to allow creation of models in either a repository or the workspace. See the video after the break to take a tour.

The M5 milestone of the Kepler release brought support for UML models in CDO repositories to Eclipse. I wrote then that this provides a foundation for collaborative model editing in Papyrus using CDO. Well, that work has progressed far enough that I can offer a preview of Papyrus on CDO in action.

The Eclipse CDO and UML2 projects have both published their M5 milestones on the road to the Kepler release. In this milestone, UML models can now be shared in CDO repositories!

A lot of fixes and enhancements have gone into this milestone of both the CDO and UML2 projects to make UML models fully functional in CDO repositories. In several ways, some small and some big, UML is a peculiar EMF model. It implements some specialized structural semantics (e.g. subsetting) and awkward overrides (e.g. redefining a mutable reference as derived). It is an unique EMF model. So, quite natural that it should have required work in both CDO (to make allowances for UML) and UML2 (to conform to EMF/CDO norms) to get the two playing together nicely.

More details after the break.