The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

Deploy language

[26]

Eclipse propose several way to deploy and distribute the language created using the GEMOc approach. The most appropriate method will depend on the main usage.

Basically, it consists in launching the plugins of the language using PDE (Plugin Development Environment) offered by Eclipse.

Some Eclipse articles describe this process:

1. Deployment of languages for the Language designer

The language designer can test the language he is designing by launching a new Eclipse runtime from his development workbench.

This is done by creating a run configuration. Select "run / run Configurations" Double click on "Eclipse Application" and change the name "New Configuration" into "<YourSuperLanguage> Modeling Workbench". We can now click "Run" to start the new runtime Eclipse which indeed corresponds to the Modeling Workbench for your language.

Tip

This mode offer some fine control. For example, it is possible to put breakpoint in the DSA code in order to finely develop them.

Runtime workbench launch configuration

Figure 14. Runtime workbench launch configuration


2. Distribution of languages to the Model designer

Distributing the language concist in distributing the plugins. This typically could be done via an update site or a full eclipse package (RCP application).

  • The update site will allow to install the language in an existing Eclipse.
  • The RCP methodoly will allow to create an application with a dedicated set of plugins including the language. This application could look like a classic eclipse IDE (including java, etc) or be completly customized for a given purpose by providing only required tools.

Tip

Once the updatesite or product have been defined, you may need to automate the build. The current best practice is to use Tycho. (see also some good tutorial about this on internet.)

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.