The 6 native core plugins below are iniatilized twice, when HopEnvironment calls PluginRegistry.init (), all core plugins previously added plugins are initialized a second time (slow startup)
The sequence order:
1) HopClientEnvironment add core plugin type
2) HopClientEnvironment init plugin registry
3) HopEnvironment add engine plugin type
4) HopEnvironment init plugin registry (core + engine)
It is useful to differentiate whether the PluginType is added or registered ?
In my opinion we can solve the problem by removing the addPluginType and init methods, and keeping the registerPluginType method.