| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML> | |
| <HEAD> | |
| <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>Generating component JAR</title> | |
| </head> | |
| <BODY BGCOLOR="#ffffff"> | |
| <h2>Deploying a Feature</h2> | |
| <p>Once versions are synchronized, we can package our feature in the format fit | |
| for publishing. </p> | |
| <p>First you have to set up the build configuration. The build | |
| configuration includes information about the files and directories that should | |
| be included in the feature for each individual plug-in and fragment. There | |
| may be some design-time files and directories that should not be shipped. | |
| See <a href="pde_feature_generating_build.htm">Build Configuration</a> for | |
| details.</p> | |
| Then you can use PDE's Export Deployable Features wizard to build and export the | |
| feature. This way you are shielded from Ant scripts and your workspace is | |
| never polluted with build by-products.<ol> | |
| <li>Select <b>File>Export...>Deployable Features</b>.</li> | |
| <li>Select the feature(s) you want to export. </li> | |
| </ol> | |
| <p align="center"> | |
| <img border="0" src="images/feature-export.gif" width="470" height="550" alt="Export Features wizard"></p> | |
| <p> </p> | |
| <p>The wizard will build all the features selected and their included plug-ins | |
| and fragments. </p> | |
| <p>If the 'single deployable zip file' option is selected, everything will go | |
| into one zip file, which can then be unzipped into any Eclipse product. | |
| </p> | |
| <p>If the 'update JAR archives' option is selected, the wizard will create a JAR | |
| for every feature selected. The JAR name will be of the format: <b><feature_id>_<feature_version>.jar</b>, | |
| and will be placed in a <b>features/</b> sub-directory of the directory you | |
| specified in the wizard. The wizard will also create a JAR for every | |
| plug-in or fragment included in the feature. The JAR name will be of the | |
| format <b><id>_<version></b>.jar, and will be placed in a <b>plug-ins/ </b> | |
| sub-directory of the directory you specified.</p> | |
| <p> </p> | |
| <p>The alternative would be to build features manually:</p> | |
| <ol> | |
| <li>Right-click on the feature.xml file for your feature project and choose '<b>Create | |
| Ant Build File</b>'. This will generate a build.xml file.</li> | |
| <li>Select the build.xml file and choose '<b>Run Ant...</b>' </li> | |
| <li>In the Ant build script wizard, select the target(s) you want to run. | |
| See <a href="pde_feature_generating_ant.htm">Generating Ant Scripts</a> for | |
| details.</li> | |
| </ol> | |
| <p> <br> | |
| <a href="../hglegal2003.htm"> | |
| <img src = "../images/ngibmcpy2003.gif" alt="Copyright IBM Corporation and others 2000, 2003" border="0" width="324" height="14"></a> | |
| </p> | |
| </body> | |
| </html> |