Re: [cross-project-issues-dev] Papyrus contribution to Oxygen M3

[Laurent Goubet <laurent.goubet@xxxxxxx>]

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:

Hi Christian,

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:

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 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.

HTH,

Christian

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 1.0.0.201610250603 (org.eclipse.emf.compare.uml2.papyrus 1.0.0.201610250603) requires 'bundle org.eclipse.papyrus.uml.tools [1.0.2,3.0.0)' but it could not be found

 

Strangely enough the oep.uml.tools is contributed at the 3.0.0 version number… (http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/3.0/M3/main/plugins/?d)

 

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

 

Thanks,

Quentin

 

_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org 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@eclipse.org 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

begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr";>Obeo</a>
email;internet:laurent.goubet@xxxxxxx
url:http://www.obeo.fr
version:2.1
end:vcard