Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Acceleo/Runtime"

m (Generation engine)
Line 9: Line 9:
 
== Generation engine ==
 
== Generation engine ==
  
The generation engine can launch an Acceleo generation from an Acceleo module and and EMF model. You can see in the next screenshot a small Java program to call the Acceleo engine.
+
The generation engine can launch an Acceleo generation from an Acceleo module and and EMF model.
 
+
  
 
== Stand alone ==
 
== Stand alone ==

Revision as of 05:16, 27 January 2011

Runtime

Acceleo is based on three separate components: the compiler, the generation engine and the tooling. The acceleo runtime is composed of the generation engine and the compiler.

Compiler

The Acceleo compiler can be found in the bundle org.eclipse.acceleo.parser. In this bundle, you can use the class AcceleoParser to parse a "mtl" file and return the root of the "emtl" file. That root can then be serialized in a file with the "emtl" extension.

Generation engine

The generation engine can launch an Acceleo generation from an Acceleo module and and EMF model.

Stand alone

The Acceleo runtime can be used in a stand alone environment without any dependencies to the Eclipse IDE, as such it can be embedded in a good old Java application. Acceleo 3.1 will feature some specific Ant and Maven tasks in order to call the Acceleo compiler and the Acceleo generator in stand alone easily.



Acceleo Portal
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

Back to the top