Project Plan For OCL (Object Constraint Language), version 4.1.0 (Kepler)

Introduction

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

The plan for 4.1 was to complete the prototyping of models and solutions to the UML alignment and many other issues in the OMG OCL 2.3.1 specification.

Considerable progress was made, but not enough to permit the examples prototypes to be promoted as replacements for the legacy functionality.

The OCL to Java code generator was rewritten twice so that it now has a sound underlying model making the code simpler and more efficient and permitting optimizations to be realized easily.

The support for UML was improved so that the new functionality is now exploited within Papyrus for profiles and validation.

The project should now be in good shape to complete UML alignment and then support accurate auto-generation of Java for the many new and changed OCL constraints in the UML 2.5 specification.

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.

Release Deliverables

The release deliverables for the Eclipse (MDT) OCL 4.1 release have the same form as is found in most Eclipse projects, namely:
  • OCL All-in-One P2 repository (downloadable and update site).

Eclipse OCL 4.1 will use GIT for source control.

Eclipse OCL 4.1 will primarily target Eclipse 4.3 rather than Eclipse 3.9.

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

Table of Contents

Release Milestones

Release milestones occur at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 week; that is, until the final 4.3 release of the Platform, upon which Eclipse OCL and other projects will release simultaneously. As Eclipse OCL is a dependency of numerous other projects, Eclipse OCL will deliver its Core plugins at the +1 milestones schedule in accordance with the schedule below. Tools plugins will be two days later on the +3 schedule.
4.1.0M1Monday 20 August 2012
4.1.0M2Monday 1 October 2012
4.1.0M3Monday 12 November 2012
4.1.0M4Monday 17 December 2012
4.1.0M5Monday 3 February 2013
4.1.0M6Monday 18 March 2013
API freeze
4.1.0M7Monday 6 May 2013
Feature Freeze
4.1.0RC1Monday 20 May 2013
4.1.0RC2Monday 27 May 2013
4.1.0RC3Monday 3 June 2013
4.1.0RC4Monday 10 June 2013
KeplerWednesday 26 June 2013

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Eclipse Object Constraint Language (OCL) project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.3 release of the Eclipse Platform Project is written and compiled against version 5.0 of the Java Platform APIs, and targeted to run on version 5.0 of the Java Runtime Environment, Standard Edition. Eclipse OCL will target the same Java version as EMF and UML2, which currently require Java 5. Eclipse Platform SDK 4.3 will be tested and validated on a number of reference platforms. Eclipse OCL will be tested and validated against a subset of those listed for the platform.

Indirect dependence on version 6 of the JRE has arisen through use of the third party components such as Google Guava. This may justify raising the lower bound explicitly for Luna.

A direct dependence on version 6 of the JRE exists on ly when dynamic compilation of auto-generated Java is exploited.

Internationalization

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 Eclipse OCL project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform.

Table of Contents

Compatibility with Previous Releases

The Eclipse OCL 4.1 project will be developed in parallel, and released simultaneously, with the following projects.
  • 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.

Table of Contents

Themes and Priorities

A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

Compliance

This theme addresses issues related to the OMG OCL 2.3.1 specification adoption. The bugs related to the inherited deviations of the Eclipse OCL implementation from the OCL 2.0 specification (and consequently, OCL 2.3.1) also appear here.
  • Committed

    • [pivot] any() should return invalid rather than null for no selection [401817] (target milestone: M6)

Release Currency

The Eclipse OCL project will maintain currency with its dependencies, in particular with the EMF and MDT UML2 projects.
  • Committed

    • allInstances does not run when a profile is applied [382981] (target milestone: M6)
    • [releng] Kepler Tools builds are not installable on Indigo [393405] (target milestone: M3)

Usability

This theme addresses the need for extensibility and usability improvements of the Eclipse OCL language implementation and APIs.
  • Committed

    • [oclinecore] Unexpected errors in the OCLInEcoreEditor when reloading [382230] (target milestone: M2)
    • [essentialocl] Hover text is not available in the Essential OCL editor [399582] (target milestone: M5)
    • [editors] Disappointing performance [401953] (target milestone: M7)
    • [completeocl] Complete OCL not available for GMF diagrams [403937] (target milestone: M7)
    • [validator] Load complete OCL in QVTc editor does nothing [404064] (target milestone: M7)
    • [oclinecore] Editing an *ecore file with mega-OCL content locks out the UI [404216] (target milestone: M7)
    • [oclinecore] Preserve user whitespace in expressions [404870] (target milestone: M7)
    • [oclinecore] Improve formatting [404871] (target milestone: M7)
    • [editors] No completion assist after entering navigation operators [405228] (target milestone: M7)
    • [codegen] Introduce a CodeGen Model [406804] (target milestone: M7)

Specification

This theme addresses issues related to prototyping resolutions of problems in the OMG OCL 2.3.1 specification and enhancements in future specifications. OMG issues will be raised and RTF proposed resolutions submitted.
  • Committed

    • [oclinecore] Support OCL-style collection declarations in Ecore [392039] (target milestone: ---)
    • [library] Provide a logging function [394660] (target milestone: M7)
    • [pivot] UML multiplicities are not converted to pivot collections [400744] (target milestone: M6)

Table of Contents

Appendix Legal Notices

  • 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.

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"