- 1 Indigo Release Review - Acceleo 3.1
- 1.1 Indigo 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
Indigo Release Review - Acceleo 3.1
Indigo Simultaneous Release
Release Review and Graduation Review
Mariot Chauvin (firstname.lastname@example.org)
Release Review : Mai 11, 2011
Communication Channel : eclipse.modeling.m2t newsgroup
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
Indigo Release Highlights
New and noteworthy
- Support for documentation for templates, queries and modules.
- Support for TODO and FIXME
- Improved real time error detections with new errors detected and warning support.
- Brand new wizard for the creation of new projects and new modules.
- Documentation in completion and hover
- New outline view
- Improved support for metamodels that have not been deployed in a plugin.
- New refactoring options
Ant and Maven support
The compilation and the generation can be launched with dedicated Ant tasks and now Acceleo can generated tycho based pom.xml file to build an Acceleo project with maven.
New serialization option
Support of binary resource serialization for Acceleo modules.
Acceleo 3.1 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
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 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
1803 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
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.1 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 May 17, 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 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
- 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
Stephane Begaudeau is now committer on Acceleo
Mariot Chauvin is now committer on Acceleo and new project lead
Since the feature freeze our commitment was to follow the EMF and the MDT OCL builds as closely as possible.
Acceleo 3.1 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/17/2010 RC2 05/25/2010 RC3 06/01/2010 RC4 06/08/2010 Final 06/16/2010 3.1 06/23/2010
The schedule used is matching the schelude of the release train for "+2" projects.
The Indigo project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-indigo.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|