The early startup is not really so early. It's certainly not
something that is invoked before the choose-workspace dialog comes
up. It's more of a performance thing (how much "eager" stuff
does one really need to do?) and also a thread-safety thing (does
your bundle start expect to run in the UI thread?). In the end, I
most certainly don't want to become the early start police.
Hi Ed
On 10/12/2019 08:56, Arthur van Dorp
wrote:
Or is it just the interactions such
that no single bundle is actually to blame? Or did I install
something that should not be installed in an IDE?
Kind of Yes. My strong prejudice is that earlyStartup is a
major facility that some projects misuse as an easy way to avoid
designing an appropriately lazy application specific startup.
IMHO earlyStartup allows many 'ordinary' things to happen before
the platform is ready. Since EMF can be used by many early
registrations, EMF is very likely to feature in the startup
fight. I would back a move to require all usage of
org.eclipse.ui.startup to need signing off by the PMC and the
platform team.
(Oops, the usage of org.eclipse.ui.startup by a user
contribution to QVTo never got written out.)
Regards
Ed Willink
_______________________________________________
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
