Skip to content

Need to centralize "propertyTester" and earlyStart #237

@dvojtise

Description

@dvojtise

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 4248e8f 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.

  • 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)

fixing this should also fix these errors

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions