Christian W. Damus a écrit :
Hi, Team,
I have begun an analysis of bundle dependency refactorings to
bring the Papyrus architecture into shape at that level of
granularity in the Neon release. The principal emphases of this
effort are:
- splitting UI dependencies out of core bundles that should
provide their APIs to headless clients, for example in
automation or web-service use cases
- eliminating dependencies pointing up the layer stack, such
as infra bundles usage of UML bundles, usage of GEF 3 in
diagram framework bundles that should also support GEF 4, etc.
- realizing the componentization of Papyrus so that build and
test execution may be implemented on a finer granularity
(Hello, test execution in Gerrit)
This will necessarily be a long and probably very disruptive
process, with APIs in use all over the place moving hither and
yon or simply disappearing. The dependency analysis is being
tracked
- in bug
485220
- on the Papyrus
wiki
- in initial refactoring changes for UI dependencies in the
Infra Layer: change 63777
and change 64168
- there will be further Gerrit patches as work progresses,
always linked from the bugzilla, of course
If and when these patches start to be merged, you will find the
ground shifting under your feet as merge conflicts arise and
APIs that you were using in new code no longer resolve. It
is not yet clear if and when any of these changes will be
merged. I shall send another notice on the mailing
list when the first change is merged, which will then
effectively commit us to a Papyrus 2.0. At that time also a
Migration Guide will be published to cover those changes. The
rest of the process will then just continue as it happens, with
piecemeal refactoring patches and migration guide updates from
time to time.
Cheers,
Christian
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev