blob: f598d61b3de1d10f2abe25d902732ade2ffafa27 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<title>User Settings: Plug-in Customization</title>
<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
<tr>
<td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Plug-in Customization</font></font></b></td>
</tr>
<tr>
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
<td WIDTH="98%"> <p><b>Plug-in Customization in Eclipse 2.1</b></p>
<p>The <a href="http://help.eclipse.org/help21/topic/org.eclipse.platform.doc.isv/guide/product_config.htm?resultof=%22%70%6c%75%67%69%6e%5f%63%75%73%74%6f%6d%69%7a%61%74%69%6f%6e%22%20">Eclipse
Help</a> page describing how to customize your plug-in.</p>
<p> 1. Set default preference values calculated at runtime.
<blockquote>
<p>Call the <code>Plugin#initializeDefaultPluginPreferences() </code>method
which is implemented by subclasses of <code>org.eclipse.core.runtime.Plugin</code>.</p>
</blockquote>
<p>2. Load from the plug-in install directory.</p>
<blockquote>
<p>Load defaults from the <code>preferences.ini</code> file in the plug-in's
installation directory such as: <code>c:/eclipse/plugins/org.eclipse.core.resources_2.0.0/preferences.ini</code></p>
</blockquote>
<p>3. Load from the primary feature's plug-in.</p>
<blockquote>
<p>Load defaults from the <code>plugin_customization.ini</code> file in
the primary feature's plug-in directory.<code> c:/eclipse/plugins/org.eclipse.platform_2.0.0/plugin_customization.ini</code></p>
</blockquote>
<p>4. Load defaults from the command line.</p>
<blockquote>
<p>Users are able to specify the <code>-pluginCustomization &lt;filename&gt;</code>
command-line argument which tells the platform to load preference values
from the specified file.</p>
<p>&nbsp;</p>
</blockquote></td>
</tr>
<tr>
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
<td WIDTH="98%"> <p><b>Plug-in Customization in Eclipse 3.0</b></p>
<p>1. Set preference values calculated at runtime.</p>
<blockquote>
<p>The <code>org.eclipse.core.runtime.preferences</code> extension point
allows for an extension which defines a <code>initializer</code> element.
This extension defines a class which extends <code>AbstractPreferenceInitializer</code>.
The <code>#initializeDefaultPreferences()</code> method is called on
the subclass.</p>
<p>If the bundle/plug-in doesn't define an extension then the <code>#initializeDefaultPluginPreferences()
</code> method is called on the plug-in class if the runtime compatibility
layer is present. Due to visibility restrictions, this is done via the
<code>Plugin#internalInitializeDefaultPluginPreferences()</code> method.</p>
</blockquote>
<p>2. Load from bundle/plug-in install dir.</p>
<blockquote>
<p>Same as with Eclipse 2.1. Load preference default values from the <code>preferences.ini</code>
file in the bundle's install directory.</p>
</blockquote>
<p>3. Load defaults from customization file as specified by the product.</p>
<blockquote>
<p>Defaults are loaded from the URL as specified by the <code>preferenceCustomization</code>
property in the product.</p>
<p>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 <code>plugin_customization.ini</code> file in the primary
feature's plug-in install directory.</p>
</blockquote>
<p>4. Load defaults from file specified by command-line option.</p>
<blockquote>
<p>Same as Eclipse 2.1. Load preference default values from the file specified
by the <code>-pluginCustomization</code> command-line argument.</p>
</blockquote></td>
</tr>
</table>
</body>
</html>