| Hi, Team,
I raised a bug today [1] to report an incompatible API change in the generated UMLEditor class in the MDT UML2 project's imminent Kepler M5 milestone, which breaks compilation of a subclass in Papyrus. This raises the question of keeping Papyrus up-to-date with its dependencies throughout the Kepler development cycle.
As far as I can tell in the Buckminster build configuration, Papyrus is still building against the Juno versions of UML2, EMF, Xtext, and other components. Is this correct?
For my CDO feature work [2], and on that branch which I hope to create in the next few days, the Kepler versions of CDO (including Dawn) and UML2 will be required, because the feasibility of CDO support depends on enhancements in those components. So, questions:
- When are we planning to update Papyrus's build to use the Kepler versions of its dependencies? Would it be feasible to do this for M5?
- Currently, Papyrus still uses EMF Compare 1.3. I asked on the bug [3] when/whether it is planned to update to EMF Compare 2.x, but have no response, yet. This is important because CDO already uses EMF Compare 2.1 in Kepler, so currently it is not install-compatible with Papyrus (I can only work because I have all of the sources checked out in my workspace)
- The Xtext 2.3.1 version currently used by Papyrus also is not install-compatible with the Kepler version; as I don't have it checked out from source, I am living with numerous compilation errors in my workspace because I can't have Xtext Kepler and Juno versions both in my target. Are we planning to update to Xtext Kepler, and if so, when?
Thanks,
Christian
|
