| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML> | |
| <HEAD> | |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 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>Synchronizing versions</title> | |
| </head> | |
| <BODY BGCOLOR="#ffffff"> | |
| <h2>Synchronizing versions</h2> | |
| <h3>Automatic synchronization at build time (Recommended)</h3> | |
| If the plug-in version changes frequently and/or developers do not have access | |
| to the feature, the versions of plug-ins, fragments and included features can | |
| be set to the special value <b>0.0.0</b> that will be replaced when exporting | |
| the feature. This is especially convenient when plug-in version are automatically | |
| upgraded using the qualifier tag. | |
| <h3>UI driven synchronization</h3> | |
| <p>The versions of plug-ins and fragments should be synchronized with the | |
| version of the packaged feature so that you can manage plug-in, fragment, and | |
| feature versions consistently. Developers typically ignore individual | |
| manifest versions until it is time to deploy their features. The Update | |
| Manager uses feature versions to determine whether a plug-in is older or newer | |
| than one already installed. Plug-ins and fragments need to follow the same | |
| version number conventions so there is no confusion about which plug-in version belongs | |
| to which feature version.</p> | |
| <p>The most convenient way to synchronize versions is to pick the version of the | |
| feature and force it into all the plug-ins and fragments that the feature references. This operation updates manifest files, so you are required to close all the manifest editors | |
| before proceeding.</p> | |
| <h4>Example: Synchronizing versions in the feature editor</h4> | |
| <p>We will take our ongoing example and force the feature version (1.2.2) into | |
| "XYZ Plug-in" and "German Fragment."</p> | |
| <ol> | |
| <li>Open the component manifest editor.</li> | |
| <li>Select <b>Synchronize versions...</b> from the popup menu. A wizard will open.</li> | |
| <li>Select the first radio button ("Force feature version..."). Press | |
| <b>Finish</b>.</li> | |
| <li>Switch to the Content page verify that the versions are now | |
| 1.2.2.</li> | |
| <li>Double-click on "XYZ Plug-in" and "German Fragment" | |
| objects and verify versions in their corresponding manifest editors.</li> | |
| </ol> | |
| <p align="center"> | |
| <img border="0" src="images/feature-synchronizing.png" alt="Feature version synchronization wizard" ></p> | |
| <h3> </h3> | |
| </body> | |
| </html> |