Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Papyrus contribution to Oxygen M3

Hi, Quentin,

It would seem that the EMF Compare project's UML2 Papyrus Comparison feature was built on an older Papyrus Oxygen build, from before the bundle version was changed to 3.0 (I suppose there was some API-breaking change requiring the 3.0 version; I don't know).  What is needed to resolve this is that the EMF Compare team update their bundle dependency to encompass the 3.0 version of, testing for compatibility and possible breakage due to API changes, then push that new build to the Simultaneous Release.  But, they would presumably want to do that only after you have contributed Papyrus M3, which I think means that they would have to disable their contribution (probably only this Papyrus integration feature) in the mean-time.

So, in short, I think you’re stuck until you get help from the EMF Compare team, probably to temporarily disable their contribution of this Papyrus integration feature.  Or else, if the version bump to 3.0 in was not warranted (I’m not suggesting that it wasn’t), you could revert that back to whatever 2.x it was before.  Probably other Papyrus bundles would have to update their dependency ranges, too, in that case.



On 2 November, 2016 at 13:05:39, LE MENEZ Quentin (quentin.lemenez@xxxxxx) wrote:

Hi Everyone,


I tried to contribute our M3 build to the aggregator but it tells me that: EMF Compare UML2 Papyrus Comparison Support ( requires 'bundle [1.0.2,3.0.0)' but it could not be found


Strangely enough the is contributed at the 3.0.0 version number… (


Can someone tell me where I might have fumbled? Or what I might have missed?





cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top