This project contains a prototype Eclipse Epsilon Model Connectivity (EMC) driver for MagicDraw / Cameo Systems Modeler.
It uses gRPC to communicate with a running MagicDraw/Cameo instance.
For developer instructions, please check CONTRIBUTING.md.
Download cameo-mdplugin-*.zip from the latest release of the plugin.
Unzip it into your MagicDraw/Cameo plugins directory.
Launch MagicDraw/Cameo as usual: upon startup, the plugin will start a gRPC server which will make your models accessible to the driver. The gRPC server will shut down automatically when you close MagicDraw/Cameo.
You can tell the driver to ensure a project is opened for you (using the setProjectURL method in MagicDrawModel), or you can open a project manually and let the driver access it.
The driver can be used in several ways, as listed below.
You may want to check the sample scripts in the examples folder:
- Adding a predefined stereotype to a class
- Creating a new stereotype and adding it to a class
- Transforming a Tree EMF model to a set of classes
The gRPC server will be listening on localhost:8123 by default.
If you want to change this, edit your magicdraw.properties file, adding something like this to the end of your JAVA_ARGS:
JAVA_ARGS=... -Depsilon.emc.host=yourhost -Depsilon.emc.port=9001
You will need to configure your MagicDrawModels accordingly (via the Eclipse GUI, through the PROPERTY_HOST / PROPERTY_PORT properties, or through the setHost and setPort methods).
You should first install Epsilon following the official instructions.
You can then download the org.eclipse.epsilon*.updatesite*.zip file from the latest release, and install its plugins into your Eclipse IDE.
Once you do that, you will be able to add a new type of model to your Epsilon launch configurations, called "MagicDraw Instance".
The run-eclipse target in the examples/org.eclipse.epsilon.emc.magicdraw.examples.etl/build.xml shows how to use the driver from an Ant workflow if you are running Ant from the same JRE as the workspace.
You should only need to use the epsilon.loadModel Ant task with type="MagicDrawRemote", while specifying any <parameters> as desired.
Please check the previous link in this paragraph for the supported properties.
The run-standalone target in the examples/org.eclipse.epsilon.emc.magicdraw.examples.etl/build.xml also shows how to use the driver when the Ant workflow is not running from Eclipse's JRE.
It will require the driver, the Epsilon Ant tasks, and their dependencies to be in the classpath, and you will need to specifically mention the Java class of the driver in the impl attribute of the epsilon.loadModel task.
One easy way to populate the classpath (especially when running from inside corporate firewalls) is to download the org.eclipse.epsilon.emc.*.antdist*-ant.zip file in the latest release, unzip it, and then ask Ant to load all its .jar files into its classpath during execution:
ant -lib path/to/antdist/lib run-standaloneAnother option is to use Maven / Gradle / Ivy to automatically download all the dependencies, as done in the Epsilon standalone Ant example.
An adaptation of this approach with Maven is available in the examples/org.eclipse.epsilon.emc.magicdraw.examples.etl/pom.xml file.
The Maven artifacts for this repository are hosted in Github Packages, which requires some configuration to be accessed.
Once you have set up your authentication to Github Packages, you can access them by adding this <repository> element to Maven:
<repository>
<id>github</id>
<url>https://maven.pkg.github.com/epsilonlabs/emc-cameo</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>Note that if you are using the repository from the Maven antrun plugin, it will need to be a <pluginRepository> element instead.
To access UML profiles and stereotypes, it's best to use these methods (assuming that your model is called Model):
Model.getProfiles(): returns all theProfiles available in your project.Model.getProfile(uri): returns theProfilewith the given URI in your project.Model.getStereotype(uri, name): returns theStereotypewithin the profile with the given URI and name. Looks inside sub-profiles.
These are better than using Profile.all, which is limited to the Profile objects inside your primary model (or the package specified by your root element hyperlink, if set).