DSL Packaging and Deployment - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 312

Figure 8-1 Requirements preferences

8.2 Defining a Product

Using the Product Definition Wizard and associated Help content, we can con-
figure a requirements.product to use for deploying our product for multiple
platforms. We first configure a minimal launch configuration that includes only
those required and use it to configure the product itself. Be careful when select-
ing required plug-ins: The PDE's Add Required Plug-ins feature does not always
detect all runtime requirements.
We need to download and install the RCP delta pack into our target, to
ensure that we have the different platform launch files available. When this is
complete, we can build our product bundles from the Product Definition editor
and test on the required platforms.
Another option to building a product is to look at Amalgam's release engi-
neering builder, which comes as another example in the DSL Toolkit. The DSL
Toolkit itself is built using this method, which begins by defining a build model
to account for the parameters required to generate build scripts from a related
product model. This model-driven build approach is in its beginning stages, so I
do not discuss this in detail at this point. The PDE's build templates could some-
day be Xpand templates, and the entire build process could be driven by a sim-
ple configuration model for each project or component.

8.2.1 Deploying Source

One of the reasons I chose to use a Plug-in Project type for our DSLs will now
become apparent. As you know, the Plug-ins view in Eclipse lets you import any
plug-in into your workspace. If the plug-in was packaged with source code, you