Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
M2T/MTL Relaunch Plan
This proposal is written to declare its intent and scope.
The Eclipse M2T project aims at developing Model To Text tools and to reduce the duplicate effort involved in developing and maintaining template languages. Currently, there are three languages components within M2T : JET, Xpand and MTL being the OMG MOF Model to Text implementation.
This document focuses on proposing an implementation as an entirely new development of the OMG MOF Model to Text (Mof2Text) language. The implementation will be compliant with the core feature compliance level of the Mof2Text language to start with, then with the advanced feature compliance.
- Standalone components (based on EMF Runtime)
- Engine: The engine will generate text based on the reflective API of EMF
- Parser : the compiler creates a EMF representation of the template
- Eclipse IDE components
- Eclipse Builder with error detection and error marking
- Template editor with code completion and syntax highlighting
- Export a generator as a plugin wizard
The Eclipse MTL will be built on top of the Eclipse Platform. EMF will be used for accessing the models by the MTL execution engine and the MTL component will be integrated with the Model Workflow Engine (MWE). It will also participate in building and/or reusing some of the M2T common components like M2T-core and M2T-shared.
The MDT-OCL component will be reused to edit and parse OCL as a sub-language of MTL. It will also be used to interpret OCL by the MTL runtime engine. Reuse of the Eclipse IMP component (http://www.eclipse.org/proposals/imp/) will be considered at the beginning of the project.
The team is composed of the creators and contributors of the Acceleo code generator project (http://www.acceleo.org) and of contributors of MOF 2 Text and QVT-R OMG specifications. No initial contribution will be made for MTL since this will be an entirely new development. The team will re-use its knowledge to build an exemplary implementation of the OMG MOF To Text standard.
Proposed initial committers
- Jonathan Musset – firstname.lastname@example.org - (proposed project lead)
- Arjan Kok - email@example.com
- Wim Bast - firstname.lastname@example.org
- Cedric Brun – email@example.com
- Laurent Goubet – firstname.lastname@example.org
- IBM - Ed Merks
- IBM - Paul Elder
- Borland - Rich Gronback
- Bernd Kolb
- CEA List - France
- TATA Consultancy Services (TCS) - Sreedhar Reddy
- modeldriven.org - Cory Casanava
- Arno Haase
MTL 1.0 planned for June 2009 including standalone engine and parser, first MTL syntax support, (core feature compliance level of the Mof2Text language) Eclipse IDE components MWE integration and documentation.
In the meantime, component opening is planned for January 2008, and standalone engine will be available by June 2008.