Configuration

The Configuration page defines the content of the product and the configuration file needed to run the product.

Content

If the product is plugin-based, the Configuration page shows a Plug-ins and Fragments section where you list all the plug-ins that will make up the product. This section also provides New Plugin... and New Fragment... buttons to enable you to create new plug-ins and fragments on the fly.

If the product is feature-based, the Configuration page shows a Features section where you list all the features that will make up the product. This section also provides a New Feature... button to enable you to create new features on the fly.

Configuration File

Upon startup, the runtime reads a configuration file named config.ini located in a configuration/ subdirectory of the configuration area of an Eclipse product. This file is a standard properties file that can configure many aspects of the runtime. For a full list of the supported properties, refer to the Eclipse runtime options document.

The Generate a default config.ini file is the default option and is recommended unless you have some very specific needs. When this option is selected, PDE generates a config.ini file with the following properties:

- osgi.bundles - lists all the bundles that should be installed and optionally started once the system is up and running. This list is based on the osgi.bundles key found in the ${target_home}/configuration/config.ini file. (Note, the ${target_home} variable is the location of the target platform).
- osgi.bundles.defaultStartLevel - denotes the default OSGi start level at which a bundle should start. The default value is set to 4.
- eclipse.product - specifies the ID of the product to launch.
- osgi.splashPath - specifies one or more locations of the splash screen.

You also have the option to use an existing config.ini file which will be copied by PDE to your final product as-is.