Hi Laurent,
What I’ll do is contribute the new M3 aggregator file to the simrel repository to see if it impacts any other consumers
that will fetch/update their dependencies and deal with the problems when they arise.
I may wait a few days, for the release of M3 to get out, before doing so and will ping you as soon as it is done.
Thanks,
De : cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
De la part de Laurent Goubet
Envoyé : jeudi 3 novembre 2016 09:17
À : cross-project-issues-dev@xxxxxxxxxxx
Objet : Re: [cross-project-issues-dev] Papyrus contribution to Oxygen M3
When I contributed our M3 to the build it didn't fail so I wasn't expecting to wake up to this. I guess we're too late now to fix this for M3 but we'll try to update our dependencies asap and contribute a nightly to the aggregator so that
papyrus isn't blocked by this when they try and update next.
Laurent Goubet
Obeo
On 02/11/2016 20:50, Quentin Le Menez wrote:
I feared that it was the case but I kept a secret hope that it was something I could correct on my end. I am not a fan of rewinding versions so I will keep an eye open and see if I it gets
picked up.
Thanks for the help,
Quentin
On 2 November 2016 at 19:48, Christian Damus <give.a.damus@xxxxxxxxx> wrote:
It would seem that the EMF Compare project's UML2 Papyrus Comparison feature was built on an older Papyrus Oxygen build, from before the org.eclipse.papyrus.uml.tools
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 org.eclipse.papyrus.uml.tools,
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 org.eclipse.papyrus.uml.tools
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.
_______________________________________________ cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Laurent Goubet
Consultant
+33 2 51 13 51 42
7 Boulevard Ampère - Carquefou - France
obeo.fr |
twitter |
linkedin
|
