Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Modeling Project Simultaneous Release

A number of Modeling projects are part of the Eclipse annual simultaneous release train, with this year's train called the Ganymede Simultaneous Release. The simultaneous release began as a single update site where consumers could go to download those projects that participated. Now, the Packaging Project participates and provides releases of predefined packages. It is the goal of the Modeling project to participate in the simultaneous release and to also define and provide a Modeling package download.

As part of the release train, a number of "must do" and "should do" items are provided. This page serves to provide information on what it takes to become a part of the Modeling release and package, above and beyond which is required by participation in the larger Eclipse simultaneous release. Below are a list of criteria and responsibilities for Modeling project and components to adhere to in order to be part.


Projects and components listed here are agreeing to work with the PMC and collaborating Modeling projects to be part of the simultaneous release and packaging effort.

  • EMF
    • Query
    • Validation
    • Transaction
  • GMF
    • Runtime
    • Tooling
  • MDT
    • UML2
    • OCL
    • UML2 Tools
  • M2M
    • ATL
    • OML
  • M2T
    • JET
    • Xpand
  • EMFT
    •  ?


In order to provide a reasonable UI and usability experience for consumers, participating projects and components must define a set of capabilities for their UI contributions, as described here.

  • As EMF is the core of all Modeling activity, it should contribute the base Modeling category for others to contribute to.
  • Capability definitions should be placed in their own plug-in and feature to allow for optional installation by consumers. The goal of the Modeling package download would be to have these installed to allow for ease of configuration, while commercial products may choose to declare their own which may conflict with those provided by Modeling.

A proposed structure:


  • Ecore Modeling
  • Model Query
  • Model Validation
  • Model Transaction
  • UML2 Modeling
  • UML2 Diagramming
  • OCL Application
  • Diagram Tooling
  • ATL Transformations
  • QVT Transformations
  • JET Templating
  • Xpand Templating


  • Decide on a common definition of SDK, Runtime, etc. among participants?
  • All must use the Modeling icon for the About dialog?

Back to the top