Revision as of 10:57, 27 September 2011

3.2 Release Review - Acceleo 3.2

Mariot Chauvin (mariot.chauvin@obeo.fr)

Release Review : October 1, 2011

Communication Channel : eclipse.modeling.m2t newsgroup

Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php

Project Plan : http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-indigo.xml

3.2 Release Highlights

New and noteworthy

Acceleo 3.2 is compatible with Eclipse 3.4 (Ganymede), Eclipse 3.5 (Galileo), Eclipse 3.6 (Helios) and Eclipse 3.7 (Indigo).

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.templates") is now deprecated. It still works but a new extension point has been contributed instead ("org.eclipse.acceleo.engine.dynamic.modules").

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.

CQ 2518 - The Content includes items that have been sourced from the OMG MTL 1.0 specification : http://www.omg.org/spec/MOFM2T/1.0/

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 (http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf).

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 http://www.eclipse.org/projects/ip_log.php?projectid=modeling.m2t.acceleo

Non-Code Aspects

Unit tests

2789 unit tests are launched every day.

Code coverage is about:

• 82 % of the traceability engine
• 80 % of the compiler
• 65.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 44% of the Java source code.

An Ohloh page is available at http://www.ohloh.net/p/acceleo-eclipse/analyses/latest

APIs

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.

Documentation

The documentation that comes with Acceleo 3.2 is available in the Help menu : Acceleo Model To Text Transformation Language.

Each document of the documentation set deals with a different aspect of mastering Acceleo : There are a Plug-in Overview, a Quick Start, an Android Code Generation Tutorial, a User Guide, several short tutotials to create code generation projects, an Acceleo/OCL operations reference to describe the Acceleo/OCL library, and a Text Production Rules document.

The main documentation is the User Guide because it fully describes each and every feature of Acceleo. From the installation to the execution with a trip through the editing features, it gives an in-depth description of everything there is to know about Acceleo.

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

There is also a basic information page on the Eclipse Wiki http://wiki.eclipse.org/Acceleo

Bugzilla

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 May 17, 2011)‏

Tool usability

Localization : integrated into Babel

Standards

This implementation of Acceleo is based on the OMG MOF Model-To-Text OMG Standard : http://www.omg.org/spec/MOFM2T/1.0/

End of Life

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

Communities

Talks have been given on the following events:

• Acceleo at the Eclipse Summit Europe 2010: http://www.eclipsecon.org/summiteurope2010/sessions/?page=sessions&id=1833
• Acceleo on e4 during the modeling symposium at the Eclipse Summit Europe 2010: http://www.eclipsecon.org/summiteurope2010/sessions/?page=sessions&id=1898
• Acceleo at the Topcased Days 2011: http://www.topcased.org/index.php/content/view/53
• Acceleo at Code Generation 2011: http://www.codegeneration.net/cg2011/sessioninfo.php?session=24

Other medium:

• Activity on the M2T newsgroup (eclipse.modeling.m2t): more than 170 messages on Acceleo from June 2010 to May 2011
• Twitter account of the Acceleo project: http://twitter.com/acceleo
• Acceleo on stack overflow: http://stackoverflow.com/tags/acceleo/info

Committer Changes

None

Schedule

Acceleo 3.2 Release Plan

RC1	05/17/2010	
RC2	05/25/2010	
RC3	06/01/2010	
RC4	06/08/2010	
Final	06/16/2010	
3.2	06/23/2010

Project Plan

The Acceleo 3.2 project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-indigo.xml

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.