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


This page provides the required docuware for the EMF Validation 1.6.0 Release Review, as part of the upcoming Juno Simultaneous Release.


The EMF Validation project provides the following capabilities.

  • Constraint Definition - Provides API for defining constraints for any EMF meta-model (batch and live constraints).
  • Customizable model traversal algorithms - Extensibility API to support meta-models that require custom strategies for model traversal.
  • Constraint parsing for languages - Provides support for parsing the content of constraint elements defined in specific languages. The validation framework provides support for two languages: Java and OCL.
  • Configurable constraint bindings to application contexts - API support to define "client contexts" that describe the objects that need to be validated and to bind them to constraints that need to be enforced on these objects.
  • Validation listeners - Support for listening to validation events.


New in this release

No significant events have occurred with the Juno release. EMF Validation is undergoing it's participation in the Eclipse Simultaneous release as it has for each and every release. This is the seventh yearly June release of EMF Validation.

Accordance with project plan themes and priorities

See the EMF Validation project plan at


APIs have not changed this release.

  • The project lead certifies that the requirements for Eclipse Quality APIs have been met for this release.
  • Metamodel definitions and corresponding implementations are considered APIs.
  • API Tooling has been employed.


  • No change.

Tool Usability

  • Tools haven't changed.


Nothing has been deprecated.


There was minimal activity in Bugzilla during the the Juno release.


Not applicable.

UI Usability

Nothing has changed.


EMF Validation is a “+1” component in the simultaneous release.

M1	08/16/2011	
M2	09/27/2011	
M3	11/08/2011	
M4	12/13/2011	
M5	01/31/2012	
M6	03/14/2012	API freeze
M7	05/02/2012	Feature Freeze
RC1	05/16/2012	
RC2	05/23/2012	
RC3	05/30/2012	
RC4	06/06/2012	
Juno	06/22/2012


  • Interaction in Bugzilla
  • Activity on the EMF newsgroup
  • Collaboration with other projects at Eclipse

Commiter Changes

No committers changes on EMF Validation for Juno. Anthony Hunter is the lead of the the EMF Validation component and currently the only active committer on EMF Validation.

IP Issues

The EMF Validation component leadership verifies that:

  • the about files and use licenses are in place as per the Guidelines to Legal Documentation.
  • all contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
  • all significant contributions have been reviewed by the Foundation's legal staff.
  • all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
  • all Contribution Questionnaires have been completed.
  • the "provider" field of each plug-in is set to "Eclipse Modeling Project“.
  • the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
  • any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
  • any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.

The EMF Validation Project IP log in located at

Project Plan

The current project plan is available from

Draft development plan for next release is not yet available.

Back to the top