- 1 3.2 Release Review - Acceleo 3.2
- 1.1 3.2 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 Committer Changes
- 1.12 Schedule
- 1.13 Project Plan
- 1.14 Legal Notices
3.2 Release Review - Acceleo 3.2
Mariot Chauvin (email@example.com)
Release Review : October 1, 2011
Communication Channel : eclipse.modeling.m2t newsgroup
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
3.2 Release Highlights
New and noteworthy
The interpreter view allows the user to enter Acceleo expressions and to execute them without the need to launch a generation.
This new view is available directly in the Acceleo perspective.
Performances improvements in the compilation and the tooling.
JRE selection in the new project wizard
When creating a new Acceleo project, you can now choose the JRE of your choice.
The compilation has been improved and as such compiled Acceleo modules (".emtl" files) are now way smaller.
New dynamic modules extension point
Users who were using the dynamic module extension point to extends a generator can now use the brand new extension point created to contribute to a specific generator.
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").
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/ CQ 5533 - Google Collections Version: 1.0 (PB Orbit CQ3830)
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
2789 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
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
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.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
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 September 27, 2011)
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 Code Generation 2011: http://www.codegeneration.net/cg2011/sessioninfo.php?session=24
Talks will be given during EclipseCon Europe 2011.
- Activity on the M2T newsgroup (eclipse.modeling.m2t): more than 80 threads 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
Acceleo 3.2 Release Plan
RC1 10/10/2011 RC2 10/11/2011 RC3 10/12/2011 RC4 10/13/2011 Final 10/14/2011 3.2 10/15/2011
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-3_2_0.xml
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.
|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|