Plug-in Customization in Eclipse 3.0
1. Set preference values calculated at runtime.
org.eclipse.core.runtime.preferences extension point
allows for an extension which defines a
This extension defines a class which extends
#initializeDefaultPreferences() method is called on
If the bundle/plug-in doesn't define an extension then the
method is called on the plug-in class if the runtime compatibility
layer is present. Due to visibility restrictions, this is done via the
2. Load from bundle/plug-in install dir.
Same as with Eclipse 2.1. Load preference default values from the
file in the bundle's install directory.
3. Load defaults from customization file as specified by the product.
Defaults are loaded from the URL as specified by the
property in the product.
For backwards compatibility if a feature does not define a product,
then the Update code will automatically fill in this property value
to be the
plugin_customization.ini file in the primary
feature's plug-in install directory.
4. Load defaults from file specified by command-line option.
Same as Eclipse 2.1. Load preference default values from the file specified
-pluginCustomization command-line argument.