Add a new IEngineAddon that implements the IEngineAddon api as a web protocol. (org.eclipse.gemoc.executionframework.addon.eaop.server)
Add a new Websocket server plugin allowing to easily offer websocket endpoint from Eclipse. (org.eclipse.gemoc.ws.server and org.eclipse.gemoc.commons.utils)
Add an JSONSchema to protocol generator. (protocols/generators/ts/JSONSchema2APIProtocolGenerator) it is able to generate java API, Typescript API, plantuml description from the schema.
Add EAOP (Engine AddOn Protocol) definition and generated Java and TS API, (protocols/engine_addon_protocol)
Updated documentation with content generated from the protocols
Bump tycho to 2.7.0
Add Jetty 10 in the studio (directly from maven central as there is no update site providing it)
Add support for mapstruct in order to deal with DTO mappings.
Current limitations:
The protocol is still incomplete, the events are currently implemented as notification (ie. non blocking)
Add org.eclipse.gemoc.gemoc_studio.targetplatform/gemoc_studio_dev.target for convenient development : it allows developing the GEMOC studio on any eclipse by using latest GEMOC studio update site as a base and without having to import all gemoc projects in the workspace. The other file gemoc_studio_dev.target on the other hand is dedicated to the build. ie. it only imports external dependencies.
Description
org.eclipse.gemoc.executionframework.addon.eaop.server
)org.eclipse.gemoc.ws.server
andorg.eclipse.gemoc.commons.utils
)protocols/generators/ts/JSONSchema2APIProtocolGenerator
) it is able to generate java API, Typescript API, plantuml description from the schema.protocols/engine_addon_protocol
)Current limitations:
Current protocol:
Changes
.targetplatform
file (and using 0.0.0 versions in it ) This is required to use the new support of maven central artefact in targetplatform files (cf. https://www.modumind.com/2021/01/11/including-maven-artifacts-in-an-eclipse-rcp-target-platform/) (if tdp tooling receive an update we will consider reusing it)org.eclipse.gemoc.gemoc_studio.targetplatform/gemoc_studio_dev.target
for convenient development : it allows developing the GEMOC studio on any eclipse by using latest GEMOC studio update site as a base and without having to import all gemoc projects in the workspace. The other filegemoc_studio_dev.target
on the other hand is dedicated to the build. ie. it only imports external dependencies.Contribution to issues
Some content in this PR actually comes from earlier works that wasn't ready for deployment (cf. https://github.com/eclipse/gemoc-studio-modeldebugging/pull/169) (for example the
org.eclipse.gemoc.ws.server
and some other componentCompanion Pull Requests