DTP 1.5 Development Environment

From Eclipsepedia

Jump to: navigation, search

Back to DTP Main Page


As described in the DTP 1.5 build documentation, we are building against Eclipse 3.2.2 (with associated EMF and GEF versions) and a Sun 1.4 VM. The primary test environment is the latest of Eclipse 3.3 (with associated EMF and GEF versions) and a Sun 1.5 VM. We are doing this in an attempt to make DTP 1.5 available on both 1.4/1.5+ VMs and Eclipse 3.2.2/3.3. In order for this to work, all DTP committers must be developing against a Eclipse 3.2.2 target platform with a 1.4 VM. Doing otherwise runs the very real risk (as has been demonstrated by a number of build breakages during 1.5) that Eclipse 3.3 or 1.5 VM features will be used, hence invalidating the code in the build environment. Given the on-going problems in this area, this page is designed to explain how to achieve the required configuration, regardless of your preferred Eclipse development version.

DTP 1.5 Development Environment

You can develop DTP 1.5 using Eclipse 3.2.x or 3.3 (perhaps other versions too, if you wish), but you must be sure to set the proper target platform. The target platform configuration is located in Window-->Preferences...-->Plug-in Development-->Target Platform and looks like:


To use this for developing DTP 1.5, you should have:

  • An Eclipse 3.2.2 (with associated EMF and GEF versions) location
  • An Eclipse 3.3, latest M or RC (with associated EMF and GEF versions) location
  • Sun Java 1.4 VM installed
  • Sun Java 1.5 VM installed

Next, you need to make sure that the target platform is set correctly. In the configuration dialog shown above, you can Browse... to the necessary folder. For standard DTP 1.5 development, this should be the folder containing Eclipse 3.2.2. Select the folder, and verify that all the expected plug-ins appear in the dialog list. If you are developing in Eclipse 3.2.2, then the default selection to your development environment will be fine.

Next, you need to make sure that the correct VM version is being used. Check the second tab on the Target Platform dialog: