Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
<html lang="en">
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2012. 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">
<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/"></script>
<title>Organizing Manifest Files</title>
<link href="../../book.css" rel="stylesheet" type="text/css">

<h1>Organizing Manifest Files</h1>

<p>PDE provides an <strong>Organize Manifests</strong> wizard to help ensure that
 the information in your Manifest is up to date. 
 The wizard is available through the <strong>Plug-in Tools</strong> menu after right clicking
 on a plug-in project's MANIFEST.MF or plugin.xml files.

<p><img src="../../images/pde_actions/organize_manifest.png" alt="Organize Manifest" >

<h3>Export Package Options</h3>
<p>The <strong>Ensure that all packages appear in the MANIFEST.MF</strong> option
 will add Export-Package declarations for any package in the project which is not
 already exported.

<p>The <strong>Mark as internal all packages that match the following filter</strong>
 option can be used to modify the visibility of any Export-Package declarations in a
 project's Manifest.  The <strong>Package filter</strong> field should contain a
 regular expression used to match the names of packages that should be marked internal. 
 Packages marked as internal will not be available for use by other bundles. 
 Refer to the <a href="../editors/manifest_editor/access_rules.htm">Access Rules</a>
 document for more information on package visibility.

<p>The <strong>Remove unresolved packages</strong> option will remove any Export-Package
 entries which cannot be resolved.  There are a variety of reasons why an exported package
 cannot be resolved, but the most common reason is because it does not exist in the

<p>The <strong>Calculate 'uses' directive for public packages</strong> option will
 handle the complicated computations for the 'uses' directive for any packages that
 other bundles have access to.  Since the computations are complex and require code
 introspection, this operation may take more time than other organization operations. 
 This operation has been marked as a long-running operation.

<h3>Dependency Options</h3>

<p>The <strong>Handle unresolved dependencies</strong> option allows you to clean up
 your Manifest by removing any unresolved dependencies. 
 A dependency may be unresolved for a variety of reasons, such as an optional plug-in
 being missing from the current configuration.  For this reason, you may elect to handle
 unresolved dependencies by either <strong>removing them</strong> from the Manifest or
 <strong>marking them as optional</strong>.

<p>The <strong>Remove unused dependencies</strong> option can help you identify and
 remove any unused dependencies currently defined in the Manifest. 
 Unused dependencies may require additional unnecessary bundles to be installed in a
 runtime.  This operation analyzes your project's code to check for references and
 may take more time than other organization operations.  This operation has been
 marked as a long-running operation.

<p>The <strong>Add required dependencies</strong> option inspects the project's
 code to try to add additional dependencies which are not currently included in
 the manifest. 
 This operation will only find new dependencies for bundles listed in the
 <strong>Automated Management of Dependencies</strong> section of the
 <a href="../editors/manifest_editor/dependencies.htm">Dependencies page</a> in
 the <a href="../editors/manifest_editor/editor.htm">Manifest Editor</a>. 
 This examination may take more time than other organization operations and has
 been marked as a long-running operation.

<h3>Miscellaneous Options</h3>

<p>The <strong>Remove unnecessary lazy activation headers</strong> option will
 remove lazy activation headers if a Bundle-Activator is not defined. 
 If a bundle has nothing to contribute when it is started, a lazy activation
 header is not necessary.

<p>The <strong>Delete unnecessary plug-in manifest files</strong> option will
 remove plugin.xml files if a plug-in doesn't contribute any extension or 
 extension points.

<h3>Internationalization Options</h3>

<p>The <strong>Prefix icon paths in plug-in extensions with a $nl$ segment</strong>
 option will modify icon paths to allow fragments to contribute unique icons for
 different locales.

<p>The <strong>Remove unused keys from the plug-in's properties file</strong>
 option will help find and remove unused keys in the plug-in's properties file.

New to GrepCode? Check out our FAQ X