Re: [mdt-papyrus.dev] Keeping Up with Kepler

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

The 25-Jan 0.10.0 N-build exploits an OCL API introduced at Kepler M2 to support Xtext editing in Profiles, so some parts of the build are more recent than Juno.

     Regards

        Ed Willink

On 29/01/2013 15:06, Christian W. Damus wrote:

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?