Skip to main content

Project Plan For GMF Tooling, version 3.2.0


This document lays out the feature and API set for the Luna release of the Eclipse Graphical Modeling Framework Tooling (GMF-T) Project, version 3.2.0.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:

  • GMF Tooling source code release, available as versions tagged "R3_2" in the project's GIT repository.
  • GMF Tooling SDK (includes sources, examples, documentation and runtime components) (update site only).
  • GMF Tooling Runtime binary distribution (downloadable zip and update site).

Table of Contents

Release Milestones

Release milestones occur at roughly 6 week intervals and follow the Platform milestone releases by approximately 2 weeks; that is, until the final 4.3 release of the Platform, upon which GMF Tooling and other projects will release simultaneously. It is anticipated that GMF Tooling will synchronize its release milestones with the Luna release schedule for +3 components.


GMF Tooling will produce maintenance releases to align with the Luna SR releases, that includes the Eclipse Platform 4.4.1 and 4.4.2 releases. GMF Tooling may produce interim maintenance releases in addition to these in order to satisfy clients requests.

  • 9/26/2014 (last Friday of September) - GMF Tooling 3.2.1 maintenance release (Luna Service Release 1)
  • 2/27/2015 (last Friday of February) - GMF Tooling 3.2.2 maintenance release (Luna Service Release 2)
  • A list of issues indicated for the 3.2.x maintenance stream can be found in Bugzilla.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments.

The GMF Tooling (GMF-T) 3.2 project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.4 release of the Eclipse Platform Project is written and compiled against versions 1.5 and 1.6 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition. GMF-T will target the same Java version as EMF, which currently also requires Java 5. Eclipse Platform SDK 4.4 will be tested and validated on a number of reference platforms. GMF-T 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 GMF Tooling 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 3.2

GMF-Tooling project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the GMF-T will be compatible with the corresponding milestones for each of these projects, and delivered the appropriate offset.

  • Eclipse Platform SDK, version 4.4
  • Eclipse Modeling Framework (EMF), version 2.10
  • Graphical Modeling Framework Runtime / Notation, version 1.8.

Therefore, the GMF tooling release will be compatible with these versions and will publish binary and source compatibilities with migration guides on subsequent releases.

Table of Contents

Themes and Priorities

The project has identified major areas of work, that will be the priorities for this development cycle. These areas will address the major themes identified by the Eclipse Requirements Council ( Eclipse Themes and Priorities).


  • Committed

    • [plan] Obsolete generation targeting JDK1.4, assume generics, annotations and for-each [380983] (target milestone: ---)
  • Proposed

    • [plan] Revive RCP-generation by targeting E4 [417995] (target milestone: 3.2)
    • [plan] Deprecate the old Xpand GMF Tooling templates after finalizing the switch to Xtend2 [418006] (target milestone: 3.2)

Design for Extensibility

  • Proposed

    • [plan] tracebility between generated diagram code and source templates [417991] (target milestone: 3.2)
    • [plan] Tools to assist users with the switching custom GMF-T templates to Xtend2 [418007] (target milestone: 3.2)

Ease Of Use

  • Committed

    • GMFT to allow define dynamic behavior via GMFTool model [386834] (target milestone: 3.2)
    • [plan] Support diagrams for medium / big semantic models [417980] (target milestone: 3.2)
    • [plan] Support visual structure of the diagram canvas [417982] (target milestone: 3.2M4)
    • Support for diagrams with semantic properties directly mapped to graphical properties [386832] (target milestone: 3.2)
    • More icons-oriented features for GMF-T generated editors [388850] (target milestone: 3.2)
    • [plan] Diagram outline support [417987] (target milestone: 3.2)
    • [plan] Model how to dynamically choose between different shapes in runtime. [417992] (target milestone: 3.2M4)
    • Support GMFT toolsmith with ability to use debugger for codegen / M2M stages [390323] (target milestone: 3.2M4)
  • Proposed

    • Improve validation for GMFT input / codegen models [390317] (target milestone: 3.2)
    • [plan] Allow to plug the custom compartments L&F into the generated diagram [417997] (target milestone: 3.2)
    • [plan] Support BPMN/Activity swimlane-like behavior as a first class citizen for generation [418002] (target milestone: 3.2)

Lower Entry Barrier

  • Proposed

    • Provide rich set of custom shapes as a sample/library [388849] (target milestone: 3.2)
    • Set of exemplary editors for GMFT similar to 7languages pack for XText [390321] (target milestone: 3.2)
    • [plan] Native diagramming support for XCore semantic models [417985] (target milestone: 3.2)

Table of Contents

Back to the top