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

Difference between revisions of "OCL"

(Retention Policy)
(Retention Policy)
Line 56: Line 56:
  
 
=== Retention Policy ===
 
=== Retention Policy ===
MDT/OCL doesn't have any special projec-specific API retention policy, so it's tight to the general [[Eclipse/API_Central/Deprecation_Policy | Eclipse Project guidelines on API deprecation and removal]]
+
MDT/OCL doesn't have any special project-specific API retention policy, so it follows the general [[Eclipse/API_Central/Deprecation_Policy | Eclipse Project guidelines on API deprecation and removal]]
  
Concerning the distributions in zip files which are downloadable from the [http://www.eclipse.org/modeling/mdt/downloads/?project=ocl project downloads] web page:
+
For ZIP file distributions which are downloadable from the [http://www.eclipse.org/modeling/mdt/downloads/?project=ocl project downloads] web page:
* Formal/Official Release  distributions (including service releases) will be available forever.
+
* Formal/Official Release  distributions (including service releases) will be available for as long as the corresponding Eclipse platform is available.
* Milestone distributions are stable versions which are used between releases, so they are kept until the official release comes up.
+
* Milestone and Release Candidate distributions which are stable versions preceding a releases. After the M3 milestone, the three most recent distributions will be available.
 
* Integration/Interim distributions are used between milestones. When a new milestone distribution appears, integration distributions are removed (the last one is always kept).
 
* Integration/Interim distributions are used between milestones. When a new milestone distribution appears, integration distributions are removed (the last one is always kept).
* Nigthly distribution are usually generated from nightly builds for internal purposes. We don't guarantee any retention of said distributions.
+
* Nightly distribution are usually generated from nightly builds for internal purposes. There is no guarantee of any retention.
  
Regarding the provided P2 repositories. The following policy applies:
+
For the P2 repositories, the following policy applies:
* Formal/Official Release P2 repositories are kept forever.
+
* Formal/Official Release P2 repositories are kept for as long as the corresponding Eclipse platform is available.
 
** Helios Release P2 repository: http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/
 
** Helios Release P2 repository: http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/
* Milestones P2 repositories are kept until the Official release arrives.
+
* The three most recent Milestone and Release Candidate P2 repositories are kept until the Official release arrives.
 
** Indigo Milestones P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/3.1.0/
 
** Indigo Milestones P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/3.1.0/
 
* We only keep one P2 repository with the last integration build.
 
* We only keep one P2 repository with the last integration build.
 
** Indigo Interim P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/interim/3.1.0/
 
** Indigo Interim P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/interim/3.1.0/
* We only keep one P2 repository with the last nigthly build.
+
* We only keep one P2 repository with the last nightly build.
 
** Indigo Nightly P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/3.1.0/
 
** Indigo Nightly P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/3.1.0/
  

Revision as of 07:03, 12 January 2011

OCL is an implementation of the Object Constraint Language (OCL) OMG standard for EMF-based models.

The OCL component provides the following capabilities to support OCL integration:

  • Defines APIs for parsing and evaluating OCL constraints and queries on EMF models.
  • Defines Ecore and UML implementations of the OCL abstract syntax model, including support for serialization of parsed OCL expressions.
  • Provides a Visitor API for analyzing/transforming the AST model of OCL expressions.
  • Provides an extensibility API for clients to customize the parsing and evaluation environments used by the parser.

The additional OCL Examples and Editors component provides interactive support for OCL:

  • Provides an Interactive OCL Console to evaluate queries on models.
  • Provides an OCLinEcore Xtext editor for OCL embedded in an Ecore meta-model.
  • Provides a CompleteOCL editor for an OCL document complementing a meta-model.
  • Provides an EssentialOCL editor for individual OCL expressions.

The OCL parser is generated by the LALR Parser Generator, a SourceForge project, licensed under the EPL v1.0. Download it from the LPG home page. This site includes the generator executable required to regenerate the parser code.

New and Noteworthy

You may want to check the New and Noteworthy features of the MDT/OCL releases.

Example Code

Articles

Other documentation

Releases and Development

Planning

API Changes

Retention Policy

MDT/OCL doesn't have any special project-specific API retention policy, so it follows the general Eclipse Project guidelines on API deprecation and removal

For ZIP file distributions which are downloadable from the project downloads web page:

  • Formal/Official Release distributions (including service releases) will be available for as long as the corresponding Eclipse platform is available.
  • Milestone and Release Candidate distributions which are stable versions preceding a releases. After the M3 milestone, the three most recent distributions will be available.
  • Integration/Interim distributions are used between milestones. When a new milestone distribution appears, integration distributions are removed (the last one is always kept).
  • Nightly distribution are usually generated from nightly builds for internal purposes. There is no guarantee of any retention.

For the P2 repositories, the following policy applies:

N.B: This policy has been created the 24th, December, 2010.

Architecture

The remainder of this section has links to pages of interest primarily to those developing the OCL component.

Development Environment

Release Engineering

Related Links

Back to the top