Project Plan For Model Development Tools (MDT), version Kepler

Table of Contents

• Introduction
• Release Deliverables
• Release Milestones
• Target Environments
• Compatibility with Previous Releases
• Themes and Priorities
• Appendix

This document lays out the feature and API set for the seventh annual release of the Eclipse Object Constraint Language (MDT OCL) Project, version 4.1.0.

The original plan for a major version increment to 4.0 was abandoned in favour of a 3.2 increment, however tight coupling to MDT/UML2, which plans a major increment, mandates the increment to 4.0 for the overall project, features and UML-dependent plugins. The non-UML-dependent plugins have a minor increment to 3.2. Newly UI plugins start at 1.0.

Versions 3.0 and 3.1 saw the introduction of Xtext-based editors and an associated rewrite of the meta-models and evaluator to prototype a UML-aligned pivot meta-model on behalf of OCL 2.3.1 and to use a model for the OCL Standard Library. This functionality was provided in Examples plugins. The planned promotion of these Xtext-based editors and the associated pivot meta-model from Examples to Core/Tools plugins has been deferred till Kepler since the code was not ready and the timescales for review were totally unreasonable.

In version 4.1, the Xtext-based editors and pivot meta-model will be promoted from Examples to Core/Tools plugins and the very slow process of deprecation of the old Ecore and UML bindings will begin. The Core plugins will provide non-UI functionality; the Tools plugins will provide the IDE comprising editors and consoles.

Version 4.0 introduces a preliminary OCL to Java code generator so that OCL embedded in Ecore may be directly genmodelled and so that OCL-defined well-formedness rules can be used for validation within the editors.

Version 4.0 introduces an ability to load Complete OCL documents for use in third party applications such as the Ecore generated Editors and Xtext generated editors so that user-defined meta-model constraints can augment validation.

The Examples API has been revisited to facilitate re-use by OCL-derived languages such as QVT.

Note that, since the OMG OCL 2.3.1 standard suffers from significant ambiguities and conflicts making a compliant implementation impossible, Eclipse (MDT) OCL 4.1.0 release is a best endeavours attempt to establish a coherent interpretation of the OMG OCL 2.3.1 and to prototype resolutions and auto-generation of the OMG OCL 2.5 standard. Two of the Eclipse (MDT) OCL committers are also members of the OMG Revision Task Force that resolves the specification issues.

• OCL All-in-One P2 repository (downloadable and update site).

Eclipse (MDT) OCL 4.1 will use GIT rather than CVS for source control.

Eclipse (MDT) OCL 4.1 will primarily target Eclipse 4.3 rather than Eclipse 3.9.

Eclipse (MDT) OCL 4.1.0 source code will be available as versions tagged "R4_1" in the project's GIT repository.

• Eclipse Platform SDK version 4.3
• Eclipse Modeling Framework (EMF) version 2.9
• Model Development Tools (MDT) UML2 version 4.1

As described above, the Eclipse OCL 4.1.0 release should address usability of the editors. The main OCL plugins should be unaffected, but the associated examples plugins may be revised significantly.

Again as described above, the Eclipse OCL 4.1.0 release for Kepler will introduce significant new APIs in a new namespace that replaces the old. The old namespace will be deprecated once all Simultaneous Release projects have migrated to the new namespace.

• Java is a trademark or a registered trademark of Oracle Corporation.
• OCL, QVT, UML and OMG are trademarks or registered trademarks of the Object Management Group, Inc.
• All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.