Java Reference
In-Depth Information
<targeturidef
targeturi="platform:/resource/example/modeling.config"
/>
</qvto.interpretedTransformation>
TIP
When launching QVT Ant tasks within Eclipse, be sure to select
Run in
the Same JRE As the Workspace
on the
JRE
tab of the Ant launch
configuration so that the custom tasks are found.They're located within the
antTasks.jar
file in the
org.eclipse.m2m.qvt.oml.runtime
bundle.
Returning to our mindmap example, let's use an instance of our
mindmap
model
to produce a corresponding
requirements
model. Looking at the two domain
models developed earlier, we can see that several elements should map nicely.
When we created each DSL, we anticipated transforming from one to the other,
which makes it easier but is not always the case. Using preexisting models or
models that have different purposes does not typically make for such a clean
mapping.
Operational QVT and Amalgam's DSL Toolkit provide projects with the
appropriate nature and builder, so we don't need to manually add this nature to
our DSL project. If you want to add transformations to another type of project,
you can do this by opening the
.project
file in a text editor and adding the fol-
lowing content:
<buildSpec>
<buildCommand>
<name>org.eclipse.m2m.qvt.oml.QvtBuilder</name>
<arguments>
<dictionary>
<key>src_container</key>
<value>transforms</value>
</dictionary>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.m2m.qvt.oml.project.TransformationNature</nature>
</natures>
Search WWH ::
Custom Search