The release deliverables have the same form as is found in most Eclipse projects, namely:
- Acceleo SDK (includes runtime and tooling components, with sources, examples, and documentation) (downloadable and update site).
- Acceleo runtime binary distribution (downloadable and update site).
- Acceleo examples (downloadable and update site)
- Acceleo tests (downloadable and update site)
API compatibility. Acceleo 3.3 will be compatible with the extension points defined in Acceleo 3.0, 3.1 and 3.2 but some Java APIs may be deprecated and replaced with new APIs.
Workspace compatibility. A workspace being used with Acceleo 3.0, 3.1 or 3.2 will still open and work with Acceleo 3.3. In general, though, once a workspace is opened with Acceleo 3.3 there is no guarantee it will continue to work with older versions (that is, there may be some one-time migration of some workspace meta data that prevents it being usable in older versions.
Project compatibility. A project being used with Acceleo 3.0, 3.1 or 3.2 will stay compatible with Acceleo 3.3.
The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. Likewise, the Acceleo project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the time frame for availability.
The acceleo project depends upon the Platform and other projects, which are mostly "pure" Java. Acceleo 3.3.0 will be compatible with Eclipse Ganymede, Galileo, Helios, Indigo and Juno. EMF is used throughout Acceleo both for its inner mechanics and accessing the target models. The MDT-OCL component is reused to edit, parse, and interpret OCL as a sub-language of Acceleo. Acceleo will target the same Java version as EMF, which currently requires Java 5. It will also be tested on the latest release of Java 6 and Java 7. Acceleo will be tested and validated against Eclipse SDK 3.4.2, 3.5.2, 3.6.2, 3.7.2, 3.8.0 and 4.2.0.
Support for Eclipse 3.8 workbench
Advanced feature compliance
- Standalone Component.
- Advanced feature compliance level of the MOF Model-To-Text language.
- Keep the user code you typed manually : User tags and JMerge support.
- Complete Acceleo Runtime library.
- Java developer facilities : Java extensions and Properties files.
- Files encoding.
- MTL Syntax Documentation.
- Stabilization of the tooling
- Stabilization of the traceability
- Stabilization of the compilation
- Maven build, deployment and launch
Bugs for the next release
The work on the next release can be followed on the Eclipse Bugzilla thanks to the following bug entries.
Eclipse IDE components
- 2 modes for the Eclipse Builder : The fully OMG-compliant standard mode and the EMF addict mode.
- Advanced code completion and quick fixes to create a template from an example.
- Overrides View : Show the workspace and the plugin generators to make it possible to easily override the behavior of the code generation.
- Traceability information : The Result view shows the synchronization between the code and the model.
- Export a generator as a plugin and build a generator on the Eclipse build server.
- Debug and Profile a code generation.
- Real time syntax error detection.
- IDE Documentation.
Integration with other tools
- Workflow facilities for acceleo.
- Compatibility with other Eclipse modeling projects like QVTo, ATL, JET, and Xpand.
- A wizard to migrate an Acceleo template from the 2.x versions to the 3.x versions.
Examples