Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Eclipse Platform Plug-in Development Environment Guide
Previous Page Home Next Page

Configuration Tab

The Configuration Tab is an advanced tab that lets you override the default configuration area location and the config.ini file content of the runtime Eclipse application you are testing.

JUnit Configuration

Configuration Area

Every Eclipse application instance has a unique configuration area which contains metadata, caches and configuration files read by the runtime and Update Manager upon startup.

Typically, the location of the configuration is not important; therefore, PDE generates a unique configuration area in its own metadata area.

By default, this area is reused by all JUnit Plug-in Test launch configurations and deleted when the launch configuration is deleted. That is why the option to Clear the configuration area before launching is on by default.

If desired, the user can set the location of the configuration area. Variables in the directory path are supported in order to make launch configurations sharable among team members.

Configuration File

Upon startup, the runtime reads a configuration file named config.ini located in a configuration/ subdirectory of the configuration area associated with the Eclipse application instance. 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 config.ini file with default content 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
  • osgi.configuration.cascaded - indicates whether this configuration is standalone or has a parent configuration to cascade up to. The default value is set to false.
  • osgi.framework - specifies the URL location of the org.eclipse.osgi plug-in
  • osgi.install.area - specifies the location of the target platform.
  • osgi.splashPath - specifies one or more locations of the splash screen.

The Use an existing config.ini file as a template option takes an existing config.ini and makes a copy of it. PDE neither adds nor removes any properties from the file. However, PDE modifies the osgi.bundles and osgi.splashPath keys by substituting their generic bundle URL values with absolute paths that reflect the actual locations of bundles on disk.

  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire