- 1 Helios Release Review - Acceleo 3.0
- 1.1 Helios Release Highlights
- 1.2 IP Issues
- 1.3 Non-Code Aspects
- 1.4 APIs
- 1.5 Documentation
- 1.6 Bugzilla
- 1.7 Tool usability
- 1.8 Standards
- 1.9 End of Life
- 1.10 Communities
- 1.11 Schedule
- 1.12 Project Plan
- 1.13 Legal Notices
Helios Release Review - Acceleo 3.0
Helios Simultaneous Release
Release Review and Graduation Review
Jonathan Musset (firstname.lastname@example.org)
Release Review : June 11, 2010
Communication Channel : eclipse.modeling.m2t newsgroup
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
Project Plan : http://www.eclipse.org/modeling/m2t/acceleo/plan-helios.xml
Helios Release Highlights
Acceleo graduates with its Helios release. This usually means the plugin grows from version 0.x to version 1.0. However, Acceleo already has a version history and an existing adopter community. In order not to unsettle this community and to stay coherent with our history, Acceleo will jump under eclipse from version 0.8 to version 3.0 (as the last released version on Acceleo.org was 2.x).
New and noteworthy
Full traceability information : View to show all the related elements between the code and the model
Quality of APIs
The component lead certifies that the requirements for Eclipse Quality APIs have been met for this release. All non-API code in "internal" packages.
End of Life Issues
4 Committers from Obeo, and 2 individual committers.
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 significant contributions of the IP log 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
706 unit tests launched on every build. 1219 unit tests launched on every day.
Code coverage is about : - 71 % of the code generation engine - 84 % of the compiler - 29 % of the UI
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 46% of the Java source code.
An Ohloh page is available at http://www.ohloh.net/p/acceleo-eclipse/analyses/latest
Metamodel definitions and corresponding implementations are considered APIs.
Non-API classes are separated from the exposed API through an "internal" package.
Commitment to provide stand-alone code generation.
API Tooling is activated on all plugins to mark exceptions within the exposed API.
The documentation that comes with Acceleo 3.0 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
Note : these figure is subject to change as the whole team is in the process of fixing bugs until the final release (this snapshot has been taken on May 26, 2010)
Localization : integrated into Babel
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.
Talks have been given on the following events:
Acceleo at Eclipse Con 2010 : Acceleo Code Generation - Let's start with an Android example and Acceleo at Eclipse Modeling Runaway 2010
Acceleo at Eclipse Summit Europe 2009 : From Acceleo.org to Eclipse Modeling
Acceleo at Eclipse Con 2009 : a Real Standard Alternative for Code Generation
Activity on the M2T newsgroup (eclipse.modeling.m2t) 308 messages on Acceleo from June 2009 to May 2010
Since the feature freeze our commitment was to follow the EMF and the MDT OCL builds as closely as possible.
Acceleo 3.0 Release Plan
M1 08/18/2009 M2 09/29/2009 M3 11/10/2009 M4 12/15/2009 M5 02/02/2010 M6 03/16/2010 M7 05/04/2010 RC1 05/18/2010 RC2 05/25/2010 RC3 06/01/2010 RC4 06/08/2010 Final 06/16/2010 3.0 06/23/2010
The Helios project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-helios.xml
- On file close
- Macro support
- Full compatibility with ATL
- Next specification version compatibility
- Starting to create a code generator from an example (To go further)
Java and all Java-based trademarks are trademarks of Oracle, Inc. in the United States, other countries, or both.
UML, OMG, EMOF, and XMI are trademarks of the Object Management Group.
Other company, product, or service names may be trademarks or service marks of others.