blob: eed68c1f09fbc44f8e54b442543ee180a63cde7e [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Product Configuration</title>
<link href="../../../book.css" rel="stylesheet" type="text/css">
<style type="text/css">
<!--
.style1 {
font-size: 18px;
font-weight: bold;
}
.style2 {
font-size: 12pt;
font-weight: bold;
}
-->
</style>
</head>
<body>
<p class="style1">Product Configuration</p>
<p>The <strong>Configuration</strong> page defines the content of the product and the configuration file needed to run the product. </p>
<p>&nbsp;</p>
<p class="style2">Content</p>
<p>If the product is plugin-based, the <strong>Configuration</strong> page shows a <strong>Plug-ins and Fragments</strong> section where you list all the plug-ins that will make up the product. This section also provides <strong>New Plugin...</strong> and <strong>New Fragment...</strong> buttons to enable you to create new plug-ins and fragments on the fly. </p>
<p><img src="../../../images/product_editor/configuration_plugins.png" alt="Configuration Plug-ins" hspace="30"> </p>
<p>If the product is feature-based, the <strong>Configuration</strong> page shows a <strong>Features</strong> section where you list all the features that will make up the product. This section also provides a <strong>New Feature...</strong> button to enable you to create new features on the fly.</p>
<p><img src="../../../images/product_editor/configuration_features.PNG" alt="Configuration Features" hspace="30"></p>
<p>&nbsp;</p>
<p class="style2">Configuration File </p>
<p>Upon startup, the runtime reads a configuration file named <EM>config.ini</EM> located in a <EM>configuration/</EM> 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 <A href="../../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse runtime options</A> document.</p>
<p><img src="../../../images/product_editor/configuration_file.png" alt="Configuration File" hspace="30"></p>
<p>The <STRONG>Generate a default config.ini file </STRONG>is the default option and is recommended unless you have some very specific needs. When this option is selected, PDE generates a <EM>config.ini</EM> file with the following properties:</p>
<UL>
<LI><STRONG>osgi.bundles</STRONG> - lists all the bundles that should be installed and optionally started once the system is up and running. This list is based on the <EM>osgi.bundles</EM> key found in the <EM>${target_home}/configuration/config.ini</EM> file. (Note, the ${target_home} variable is the location of the target platform).</li>
<LI><STRONG>osgi.bundles.defaultStartLevel</STRONG> - denotes the default OSGi start level at which a bundle should start. The default value is set to <STRONG>4.</STRONG></li>
<LI><STRONG>eclipse.product</STRONG> - specifies the ID of the product to launch. </LI>
<li><STRONG>osgi.splashPath</STRONG> - specifies one or more locations of the splash screen. </LI>
</UL>
<p>You also have the option to <strong>use an existing config.ini file</strong> which will be copied by PDE to your final product as-is.</p>
<p>&nbsp;</p>
<p>&nbsp; </p>
</body>
</html>