as the propertyTesters in the different engines are actually completely the same, we need to finish this centralization for all engines.
need to enable earlyStartup on org.eclipse.gemoc.executionframework.engine.ui
provide a property tester in org.eclipse.gemoc.executionframework.engine.ui
changes all plugin.xml to use this property tester
note: this previous partial refactoring , raises many errors in the test logs, such as
org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.gemoc.execution.concurrent.ccsljavaengine.ui was unable to load class org.eclipse.gemoc.execution.concurrent.ccsljavaengine.ui.ModelingWorkbenchEarlyStartup.
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:212)
Historically the propertyTester (used by plugin.xml to filter actions) was duplicated in each engines UI (ie. moccml engine, java engine, ...)
In order to properly work, the enclosing project must be started, so these projects were started using the early startup extension.
in https://github.com/eclipse/gemoc-studio-modeldebugging/commit/4248e8ffe18ac2ce20177673298c1d4216c2965a this was partially centralized in org.eclipse.gemoc.executionframework.engine.ui
as the propertyTesters in the different engines are actually completely the same, we need to finish this centralization for all engines.
org.eclipse.gemoc.executionframework.engine.uiorg.eclipse.gemoc.executionframework.engine.uinote: this previous partial refactoring , raises many errors in the test logs, such as
fixing this should also fix these errors