Skip to main content

Project Plan For Eclipse Java Emitter Templates (JET2) [M2T JET], version 1.1


This plan covers the fourth release of the M2T JET component of the modeling.m2t project, to be labled 1.1.0. The release is part of the Helios Simultaneous Release. It describes the features and API for the release. This project plan inherits from the Modeling Project Plan, which should be reference when consulting this plan. This plan is a living document - it will be updated at every iteration to reflect progress and changing priorities.

Release Deliverables

The release deliverables will consist of the following components:

  • M2T JET Runtime
  • M2T JET Editor
  • M2T JET Tests
  • M2T JET Examples
  • M2T JET All-in-One, combining all of the above

Note: These components may be further refined as part of the More Modular Implementation theme.

Table of Contents

Release Milestones

The project will follow the Helios +1 schedule as defined by the Google Calendar. Milestones occur at roughly 6 week intervals, and follow the Eclipse Platform milestones by approximately 1 week.

API Freeze
Feature Freeze
Helios Final06/16/2010

M2T JET will also produces maintenance releases to align with the Galileo Service Release (SR) schedule. Additional releases may be scheduled if there is client demand. The scheduled maintenance releases are:

  • Friday, September 25, 2009 - M2T JET 1.0.1 (Galileo SR1)
  • Friday, February 26, 2010 - M2T JET 1.0.2 (Galileo SR2)

The M2T JET release notes page shows the issues resolved in each release.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The M2T JET project depends upon on the Eclipse Platform and other projects, which are mostly "pure" JavaTM. The 3.6 release of the Eclipse Platform Project is written and compiled against version 1.4 of the Java Platform APIs, and targeted to run on version 1.4 of the Java Runtime Environment, Standard Edition. M2T JET will target the same Java version as the Eclipse Platform Project. Eclipse Platform SDK 3.6 will be tested and validated on a number of reference platforms. M2T JET will be tested and validated against a subset of those listed for the platform.


The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. As a result, the M2T JET project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the time frame for availability.

Table of Contents

Compatibility with Previous Releases

Compatibility of Release 1.1.0: The M2T JET project will be developed in parallel, and released simultaneously, with the following projects:

  • Eclipse Platform SDK version 3.6
  • Eclipse Modeling Framework (EMF) version 2.6
  • Unified Modeling Language (UML2) version 3.1

As stated above, each milestone release of the M2T JET project will be compatible with the corresponding milestones from these projects.

Table of Contents

Themes and Priorities

The new functionality of this release is organized into themes. A brief description of each theme is provided here. Bugzilla entries are provided for those wanting more detailed information.

More Modular Implementation

The JET implentation is currently monolothic, requiring significant portions of the Eclipse platform (Workspace, Build, Debug and JDT) as well as EMF. A more modular implementation will allow JET templates and transformations can be executed other environments environments such as OSGi applications and RCP applications. As a stretch goal, support execution in only a JRE.

In addition, make the expression language used in a template plugable. JET currently uses XPath to navigate all model types (and provides an extension framework to adapt other languages). However, some model types are more naturally accessed by other languages. Examples: OCL for UML, EL for Java objects.

Table of Contents

Back to the top