Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Feature-Description
    1. Text - a brief description of the feature and what it contains
  • Copyright Notice
    1. Text - The copyright notice for the feature.
  • License Agreement
    1. License - Most features will choose local license
    2. Text - The text of regarding the feature's license. This will be displayed to the user during installation from the update site.

Plug-ins tab

This tab should In the plug-ins tab, list all plug-ins and fragments that are should be packaged in this the feature. Optionally, you can specify a specific version of a plugin.

Dependencies tab

This tab should list the dependent features and/or plug-ins for this the feature to be installed. This is useful for used by the update mechanism in mHARP-EQ to determine what dependencies should be satisfied to install the feature. This will prevent prevents incomplete features from being installed and breaking the mHARP-EQ application.

Updating Plug-in Manifest

This section will briefly describe the part(s) of the MANIFEST.MF that are relevant for creating the update site. This is not intended to be an exhaustive overview of the MANIFEST, for more details see the Eclipse Help guide.

Overview tab

In the overview tab, the following information should be provided:

  1. ID - the unique id for the plugin
  2. Version - the version of the plugin, see the rules mentioned in the previous section for how to version your plug-ins.
  3. Name - the name of the plug-in (e.g. mHARP Buildings)
  4. Vendor - the vendor providing the plugin

Updating Site.xml

The site.xml defines what features the update site has available. The next section will discuss the different parts of the site.xml.

Site Map tab

It's recommended that you add 1 or more categories to organize your features in the site map tab and that you keep features small in size (e.g. as few plug-ins as possible). The categories will help users determine what each feature contains (e.g. Buildings, Bridges, etc) and keeping the features small will allow users to only install what they want (e.g. don't group buildings/bridges/networks/etc in the same feature). After you have created the categories and added your features to them, if you click the Build All button you will see a features and plugins folder created along with an artifacts.jar and content.jar. Those created files/folders along with the site.xml is what will go in your update site folder. See the next section for details.

Hosting your Update Site