| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| <html> |
| <head> |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <title>Feature-Based Product</title> |
| </head> |
| |
| <body> |
| <h2>Feature-Based Product</h2> |
| <p>To be able to take advantage of the Update Manager functionality and be able |
| to publish upgrades and patches to your product, your product has to be feature-based.</p> |
| <p>Creating a feature-based product using the product editor is almost the same |
| as a plugin-based product, with the only difference being the settings on the |
| Configuration page.</p> |
| <p><img src="images/product-configuration-features.PNG" width="735" height="512"></p> |
| <p>Using the <strong>New Feature...</strong> button on the <strong>Configuration</strong> |
| page of the product editor, create a feature named <em>com.example.feature</em> |
| that contains plug-in <em>com.example.xyz, </em>as described in the <a href="pde_feature_setup.htm">Feature |
| section</a> of the guide.</p> |
| <p>On the <a href="pde_feature_manifest.htm">Overview page of the feature editor</a>, |
| the feature must declare the <em>com.example.xyz</em> plug-in as its <strong>branding</strong> |
| plug-in.</p> |
| <p>Add the <em>org.eclipse.rcp</em> feature to the list of features to be included |
| in your product.</p> |
| <p>That is it!</p> |
| <p>Proceed to the Exporting a Product section as you normally would with a plugin-based |
| configuration. </p> |
| </body> |
| </html> |
