Developing Model-to-Model Transformations - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 264

Figure 6-18 TPTP manual test behavior

To simplify the development of this transformation so that the output model
is always zipped up into our *.testsuite file after each execution, a simple
Ant build script and associated builder configuration does the trick nicely. This
is the simple script to be invoked by an Ant builder configuration added to our
org.eclipse.dsl.scenario project properties:

<?xml version="1.0" encoding="UTF-8"?>
<project name="org.eclipse.dsl.scenario" default="main" basedir=".">
<target name="main">
<zip destfile="./out/scenario.testsuite"
filesonly="false"
whenempty="skip" update="false">
<fileset dir="out/">
<include name="**/*.testprofile"/>
</fileset>
</zip>
</target>
</project>

6.9 Transforming a Business Model to Java

When generating Java or another programming language from a model, it's typ-
ical to use model-to-text technologies, such as Xpand or JET. Ultimately, code-
generation templates are required to output Java from our business domain
model, so a question emerges at this point: Do we bother with an intermediate