A model-to-model transformation mapping project is a standard Eclipse plug-in that specifies a transformation provider, which is the mechanism that defines transformations. A mapping project contains at least one mapping file, also called a mapping model. When you create a mapping project, a mapping model is created in the project automatically.
Model-to-model transformation mapping projects, also called mapping projects, are Eclipse plug-ins that extend the extension point named com.ibm.xtools.transform.core.transformationProviders. By creating model-to-model transformations in transformation mapping projects, you can specify how elements in the selected source and target models, or metamodels, are related, instead of creating code that represents the implementation details of the transformation.
A mapping project can contain more than one mapping file, which is also called a mapping model. You can iteratively generate transformation source code when you modify the mapping model. When you generate the transformation source code, one externally visible transform, called MainTransform, is registered automatically, and the Java source code for a transform is generated for each mapping declaration in the mapping model.
You can specify one or more source and target metamodels when you create a mapping project. You can specify metamodels, which have .ecore as a file name extension, or UML profiles, which have .epx or .uml as a file name extension. If you specify source and target metamodels when you create a project, the necessary dependencies are added to the plug-in manifest file automatically. If you add the metamodels by using the commands in the editor area after you create the mapping project, you must add any new required dependencies to the plug-in manifest file.
To create a model-to-model transformation mapping project: