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


3.3 Release Review - Acceleo 3.3

Stephane Begaudeau (

Release Review : May 22, 2012

Communication Channel : eclipse.modeling.m2t newsgroup

Process Documentation :

Project Plan :

3.3 Release Highlights

New and noteworthy


Performances improvements in the compilation and the tooling.

Improved compilation

The compiler has been restructured to fix long standing architectural limitations

New operations

New operations are available in the Acceleo non standard library (addAll, removeAll, etc)

New documentation

The documentation has been rewritten massively

UML to Java example

The popular example UML to Java has been updated for Eclipse Juno with a brand new version

Quality of APIs

The component lead certifies that the requirements for Eclipse Quality APIs have been met for this release. All non-API code is in "internal" packages.

End of Life Issues

The extension point for dynamic templates ("org.eclipse.acceleo.engine.dynamic.modules") is now deprecated. The extension point ("org.eclipse.acceleo.engine.dynamic.templates") now does the same job.

Committer Diversity

4 Committers from Obeo, and 2 individual committers.

IP Issues

The about files and use licenses are in place as per the Guidelines to Legal Documentation.

All other 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. The other contributions of the IP log are not significant or are written 100% by employees of the same employer (Obeo) as the Submitting Committer (

All contribution Questionnaires have been completed.

The "provider" field of each plugin is set to "Eclipse Modeling Project".

The "copyright" field of each plugin is set to the copyright owner.

Any third-party logos or trademarks included in the distribution (icons, logos, etc) have been licensed under the EPL.

The Acceleo IP log is located at

Non-Code Aspects

Unit tests

2477 unit tests are launched every day.

Code coverage is about:

  • 82.9 % of the traceability engine
  • 80.6 % of the compiler
  • 61.7 % of the code generation engine

Code quality

Checkstyle activated on each distinct plug-in.

Eclemma used on a regular basis to improve test coverage.

Yourkit used on a regular basis to improve performances.

Javadoc represents more than 42.9% of the Java source code.

An Ohloh page is available at


Metamodel definitions and interfaces are considered APIs.

Commitment to provide stand-alone code generation.

Non-API classes are separated from the exposed API through an "internal" namespace.

API Tooling is activated on all plugins to mark exceptions within the exposed API.

Non-API packages are exported with an internal visibility as such they are visible but with an illegal access warning.


The documentation that comes with Acceleo 3.3 is available in the Help menu : Acceleo Documentation.

Each document of the documentation set deals with a different aspect of mastering Acceleo:

There are an Overview, a tutorial available on this wiki, a description of all the available features, a guide detailling the Acceleo language, a list of the new features, an Acceleo/OCL operations reference to describe the Acceleo/OCL library, and a Text Production Rules document.

The main documentation are the language guide and the features guide because they fully describe each and every feature of Acceleo and its language.

Basic Examples are available in the example category : UML to Java, and Ecore to Python.

There is also an Acceleo portal on the Eclipse Wiki


blocker 0 1 0 1 2
critical 0 8 0 0 8
major 4 13 0 5 22
normal 29 43 0 22 94
minor 1 2 0 1 4
enhancement 9 9 0 10 28
TOTAL 43 76 0 39 158

Note : these figures are subject to changes as the whole team is in the process of fixing bugs until the final release (this snapshot has been taken on June 5, 2012)‏

Tool usability

Localization : integrated into Babel


This implementation of Acceleo is based on the OMG MOF Model-To-Text OMG Standard :

End of Life

There are no specific end of life concerns for this release.


Talks have been given on the following events:

Talks have been given during EclipseCon 2012.

Other medium:

Committer Changes



Acceleo 3.3 Release Plan

M1	08/19/2011	
M2	09/30/2011	
M3	11/11/2011	
M4	12/16/2011	
M5	02/03/2012	
M6	03/23/2012 API Freeze
M7	05/11/2012 Feature Freeze
RC1	05/25/2012	
RC2	06/01/2012	
RC3	06/08/2012	
RC4	06/15/2012	
Final	06/27/2012 Juno release

Project Plan

The Acceleo 3.3 project plan is available at

What's next?

Legal Notices

Java and all Java-based trademarks are trademarks of Oracle, Inc. in the United States, other countries, or both.

UML, OMG, EMOF, OCL and XMI are trademarks of the Object Management Group.

Other company, product, or service names may be trademarks or service marks of others.

Acceleo Portal
Project Project · Installation
Features Acceleo Features · Runtime · Acceleo editor · Views & Perspective · Interpreter · Maven
User documentation Getting Started · User Guide · Acceleo operations reference · OCL operations reference · Text Production Rules · Migration From Acceleo 2.x · Best Practices · Videos · FAQ
Developer documentation Source code · How to contribute · Compatibility · MOFM2T specification · OCL specification
Community Professional Support · Report a bug

Copyright © Eclipse Foundation, Inc. All Rights Reserved.