| [mdt-papyrus.dev] Attention: Papyrus Refactorings for Neon M5 are Live |
Hi, Team,
The first wave of API refactorings for the Neon release is pushed to the master branch. I call your attention to some highlights, below, that I think are of particular importance for developers to ensure your uninterrupted productivity (or so I hope). Full details of changes required in clients to adapt to these API changes are provided by the Migration Guide.
These are all of the refactorings planned for the M5 milestone. More will follow in M6.
Note that all code in the papyrus.git repository that is currently being built by the master branch builds is already refactored. No refactoring actions are required of you unless:
Please do be sure to pull these changes as soon as you are able so that we can get as much testing as possible on them before the milestone build. And, if you install nightly builds in your PDE target, please do that as soon as you can.
Thanks,
Christian
Most significant is the renaming of some bundles:
are renamed as
because this EMF model is used extensively by Infra Layer bundles, and it makes sense in
that layer anyways. The packages in this bundle are similarly renamed (substitute infra
for views).
Note that because these bundles are actually renamed, p2.inf files are added to them
to teach the Equinox p2 updater about their previous names. This should ensure that an
upgrade of your PDE Target using Oomph or, of your Papyrus workbench installation, will
proceed normally and actually replace the old bundles instead of just adding the new
ones. Having both sets of bundles causes all kinds of trouble owing to EMF registration
clashes. If you have any trouble with this, for example if you end up with an installation
that has both the old and new bundles provisioned, please let me know.
There are several new bundles added, usually to separate UI-dependent APIs from headless APIs that previously were packaged together. If you work by importing all of the source projects into a workspace, instead of installing nightlies of Papyrus in your PDE target, then you will need all of these new bundles in order to ensure (a) correct compile and (b) correct run-time behaviour:
The org.eclipse.papyrus.infra.ui bundle is not strictly new, but previously it didn’t
have any APIs for other Papyrus UI components to use, so you might have entirely missed
it. Now it has lots.
Corresponding new test bundles:
New features: