Initial version of a Model Execution Protocol framework for GEMOC #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contributes some reusable elements to implement a Model Execution Protocol (Debug Adapter Protocol) in GEMOC
This first PR adds:
a (K3) Java headless engine implementing the executionframework.mep protocol if offers a set of debug feature. At this level, the classes are still abstract, and need a concrete implementation in order to: connect the user dsl and implement the websocket
a subset of GEMOC project now have a "pomfirst" subfolder that allows to recreate a more reliable dependency tree using maven dependencies (it recreates the dependencies between gemoc projects)
a jupyter notebook client that allows to have some basic interactions with a K3 MEP server.
this PR comes with eclipse-gemoc/gemoc-studio-modeldebugging#169 and eclipse-gemoc/gemoc-studio#207