Unless and until there is a pressing need for a newer version than what's in Orbit--which has a recipe that can be updated should that need arise--couldn't the Platform stop simply stop packaging its own?
That's kind of what happened - [1] and [2]. At the time Platform (PDE actually) had the need and work was initiated there was nothing in Orbit - [3].
So now that it is orbit would a PR to consume that one when M2 orbit is ready be welcome?
What happens next time PDE/JDT needs new ASM? Same dance? This doesn't sound like a good long term plan to me.
My personal opinion is that it's better to stop putting things in Orbit when upstream provides OSGi bundles in Maven central but use directly.
OK - in that case we have some specific SimRel testing to do:
1- Which bundles ends up SimRel - or do both end up there. I assume that it will be the Orbit one because it is more recent as far as p2 is concerned (not sure, just best guess).
2- Starting from the SDK, does installing features from SimRel cause both to be installed, and if so, are both resolved.
Jonah
--
Aleksandar Kurtakov
Red Hat Eclipse Team
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
