Hi Mickael,
Thank you for the positive feedback!
1)
I do not expect it to be easy, and do not suggest to literally move something to E4 space. What I suggest is closer to the generic E3->E4 migration concept: provide common building blocks in E4 to be decorated with E3 API at org.eclipse.ui*
2)
Yes, sure we will keep it as safe as possible for the downstream components.
Regards,
AF
16.12.2019 11:39, Mickael Istria пишет:
Hi,
On Mon, Dec 16, 2019 at 9:31 AM Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:
My suggestion:
1) create "org.eclipse.e4.ui.ide" bundle to be a home of shared
functionality for both E3 and E4. It may be also named
"org.eclipse.e4.ui.resources".
I think having a separate bundle for pure E4-able IDE features would make sense.
However, I'm afraid some of the features you may want to migrate to E4 are already API and cannot be moved easily.
2) put it in between of the current bundles to not break the
downstream: "org.eclipse.ui.ide" -> "org.eclipse.e4.ui.ide" ->
"org.eclipse.core.resources".
Even if you move away some features, org.eclipse.ui.ide will probably need to keep direct reference to org.eclipse.core.resources anyway.
Cheers
--
Mickael Istria
Eclipse IDE developer, for Red Hat Developers
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
