Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

OCL/New and Noteworthy/Luna

Eclipse OCL New and Noteworthy items for the Luna 4.4.0 release.

Release Overview

Milestone 1

Editors

  • 414355 JDT-style auto content assisdt is available following . and ->

OCLinEcore

  • 410682 Comments on invariants are no longer discarded

Pivot

  • 411154 Dynamic dispatch now chooses correct dispatch for inherited candidates
  • 411441 UML-style collections such as String[*] may be used as the type of e.g. a let-variable
  • 411826 excludingAll/includingAll, appendAll/prependAll added
  • 412685 Operations and EnumerationLiterals may be used in UML profile constraints
  • 412690 EList results are now BasicInternalEList rather than just BasicEList
  • 412736 Using Ecore data types such as ecore::EDouble as operation parameters no longer fails

Code Generator

  • 414040 Common Subexpression Elimination introduced to save code/remove warnings

Milestone 2

The support for rich invariants has been made extensible.

Previously:

  • the OCLinEcore editor allowed a message expression to follow the invariant name
  • the Complete OCL editor allowed a message expression to follow the invariant name
  • the message was maintained in the ExpressionInOCL::messageExpression property
  • the message was persisted in Ecore as a ...$message EAnnotation detail
  • a validation failure provoked evaluation of the message expression
  • a validation could fail with null for error/false for warning severity

Now:

  • the OCLinEcore editor allows a message expression to follow the invariant/precondition/postcondition name
  • the Complete OCL editor allows a message expression to follow the invariant/precondition/postcondition name
  • the underlying ExpressionInOCL::messageExpression property is deprecated and not used.
  • the message is persisted as a Tuple-valued expression
    • with a mandatory 'status : Boolean = <status-expression>' to give pass/fail
    • with an optional 'message : String = <message-expression>' to give a custom failure message
    • with an optional 'severity : Integer = <severity-expression>' to give a custom severity
    • with other optional tuple parts that may be useful to a custom invocation
  • the old ...$message EAnnotation detail is translated to the new Tuple form when loaded from Ecore
  • the old null/false severity capability is deprecated but used when no 'severity' part is defined

The severity Integer signifies

  • 0 - no deficiency (e.g. for an accompanying information message)
  • +ve and not zero - minor deficiency (e.g. a warning)
  • -ve - major deficiency (e.g. an error)

The use of a Tuple-valued expression provides the enrichment within the single OCL invariant expression and so avoids the need for the tooling in which the OCL expression is used to provide any cooperation. The rich invariants may therefore be used in Papyrus or Ecore or ....

Previously:

invariant nameTooShort('There must be no lower case characters in "' + name + '"'):
    name.toUpperCase() = name;

Rich invariant

invariant nameTooShort: Tuple {
        status : Boolean = name.toUpperCase() = name,
        message : String = 'There must be no lower case characters in "' + name + '"',
        severity : Integer = 1,
        quickfix : String = 'org.examples.quickfixes.ToUpper'
    }

Milestone 3

Milestone 4

Milestone 5

Milestone 6

Milestone 7

RC1

RC2

RC3

RC4

SR1

Eclipse OCL New and Noteworthy items for the Luna 4.4.1 SR1 release.


SR2

Eclipse OCL New and Noteworthy items for the Luna 4.4.2 SR2 release.

Back to the top