Customizing the deployed Launch Configuration

If the deployed the launch configuration is to executed within an MDWorkbench RCP application, you might prefer to export the MDWorkbench project as an Eclipse plug-in, instead of a a standalone JAR file.
Here are the steps:

1. Select the project to deploy in the Project Explorer.
2. Right-click Export...
3. Select Plug-In Development > Deployable plug-ins and fragments and click Next.
4. In the Destination directory, enter the dropins directory of the MDWorkbench RCP application and click Finish.

You then need to customize the deployed launch file, to reference the deployed plug-in instead of the standalone JAR file
Here are the steps:

1. Edit the generated /MyLaunchName/MyLaunchName.launch file.
2. In the classpath XML element:
   1. Remove the file attribute.
   2. Add a bundle attribute whose value is the plug-in ID of the deployed project.
3. Save the modified .launch file.

At this stage, the following deployed files are unecessary and can be safely removed:

• /MyLaunchName/MyLaunchName.classpath
• /MyLaunchName/MyLaunchName.jar

Running the launch configuration, either in the RCP application user interface and as a command line application, will use the deployed plug-in (from the dropins directory) and not the deployed standalone JAR file.

If the MDWorkbench project is modified, you just need to deploy the project as an Eclipse plug-in, as described above.

Running an MDWorkbench RCP application
Running an MDWorkbench command line application