platform-update-home/doc/eclipse_update_packaging.html

Parent Directory | Revision Log | Patch

-revision 1.17, Thu Jan 23 21:34:37 2003 UTC
+revision 1.18, Mon Jan 27 13:29:44 2003 UTC
 Line 14
  <h1> Eclipse Platform<br>
               Update Packaging Conventions</h1>
-              <font size="-1">Revision Date: 01/22/2003 9:56AM - Version:
+               <font size="-1">Revision Date: 01/27/2003 9:00AM - Version:
-.0.18</font><br>
+.0.19</font><br>
-             <a href="../../../../../hglegal.htm"><img src="ngibmcpy.gif"
+              <a href="../../../../../hglegal.htm"><img
-  border="0" height="12" width="195">
+  src="ngibmcpy.gif" border="0" height="12" width="195">
              </a>
  <p><b>Change History:</b> </p>
  <ul>
+                <li><small>2.0.19</small><small><br>
+          </small>
+     <ul>
+       <li><small>added &lt;feature &nbsp;discovery type&gt;</small></li>
+     </ul>
+        </li>
                <li><small>2.0.18</small></li>
    <ul>
-Line 132
+Line 138
    <ul>
               <li> <font size="-1">general text cleanup</font></li>
-               <li> <font size="-1">&lt;feature&gt;&lt;group&gt; support removed
+                <li> <font size="-1">&lt;feature&gt;&lt;group&gt; support
-    (will   not be in Eclipse 2.0)</font></li>
+ removed     (will   not be in Eclipse 2.0)</font></li>
                <li> <font size="-1">arch= support added to &lt;feature&gt;
  and   &lt;feature&gt;&lt;plugin&gt;</font></li>
                <li> <font size="-1">os=/ arch=/ ws=/ nl= added to &lt;fetaure&gt;&lt;data&gt;</font></li>
                <li> <font size="-1">&lt;site url=""&gt; new semantics</font></li>
-               <li> <font size="-1">corrected errors in native installer link
+                <li> <font size="-1">corrected errors in native installer
-   support</font></li>
+ link   support</font></li>
                <li> <font size="-1">defined callback query strings for browser-triggered
        processing</font></li>
-Line 155
+Line 161
       <br>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Framework">Framework</a>
        <br>
-             <a href="#Packaging_Conventions">Packaging Conventions</a>  <br>
+              <a href="#Packaging_Conventions">Packaging Conventions</a>
+ <br>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
   href="#Feature_Archive">Feature     Archive</a>  <br>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
   href="#Plug-In_Archive">Plug-In     Archive</a>  <br>
-             &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Packaging_NL">Packaging
+              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-      NL</a>   <br>
+  href="#Packaging_NL">Packaging      NL</a>   <br>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  <a href="#Translated_Feature_Information"> Translated Feature Information</a>
         <br>
-Line 201
+Line 208
               This document outlines the support for managing the delivery
  of  function     within the Eclipse platform. Also refer to the "<a
   href="http://www.eclipse.org/legal/updatemanager.html"> Eclipse.org Update
-      Manager Agreement</a> " for additional legal information governing the
+       Manager Agreement</a> " for additional legal information governing
-   use   of the Eclipse update manager function.
+ the    use   of the Eclipse update manager function.
  <h3> <a name="Changes_from_R1.0"></a> Changes from R1.0</h3>
               This section describes the major design changes from the R1.0
   Installation      and Update support and supplies rationale for each design
-Line 219
+Line 226
     is  merged  into <i>feature</i>. Features define the packaging structure
    for a group of related plug-ins, plug-in fragments, and optionally non-plug-in
     files. Features are treated purely as an installation and packaging construct.
-    They do not play a role during Eclipse plug-in execution. Features do not
+     They do not play a role during Eclipse plug-in execution. Features do
-    nest. They are simply an inclusive "manifest" of the plug-ins, fragments
+ not    nest. They are simply an inclusive "manifest" of the plug-ins, fragments
    and other files that make up that feature. If features are logically made
    up of plug-ins from "sub-features", the top-level feature "manifest" must
    be fully resolved at packaging time. <li> <b>default feature archive format</b></li>
-Line 228
+Line 235
              R1.0 components were packaged as a single Java .jar containing
   the   component    manifest as well as the actual plug-in files. The problem
   with   this approach    is lack of granularity at download time. In R2.0,
-  the feature   archive consists    of multiple separate .jars - one .jar
+  the feature   archive consists    of multiple separate .jars - one .jar per
- per  plug-in and   fragment, plus one   .jar for the actual feature information.
+  plug-in and   fragment, plus one   .jar for the actual feature information.
   The Installation   and Update support   selectively downloads only those
  jars required for the  installation. <li>    <b>site map</b></li>
                <br>
              Default Eclipse update server must contain a <i>site map</i>
  file   (site.xml).     This is an evolution of the R1.0 install.index support.
- The  rationale for    using a structured site defined by the map rather than
+  The  rationale for    using a structured site defined by the map rather
- a  "free form" web   site, is the ability to present a consistent installation
+ than  a  "free form" web   site, is the ability to present a consistent installation
-   experience for  the user. Also, this provides the necessary structure for
+    experience for  the user. Also, this provides the necessary structure
-   discovery of available   updates. Additional support for "free form" browsing
+ for    discovery of available   updates. Additional support for "free form"
-   may be considered in   future work.    <li> <b>using native install/ uninstall</b></li>
+ browsing    may be considered in   future work.    <li> <b>using native install/
+ uninstall</b></li>
                <br>
              The primary mechanism for installing and updating Eclipse features
     is  the  built-in installation and update support. Some products may instead
-Line 247
+Line 255
     Eclipse  features. However, native installers do not implement the required
     support  for understanding the Eclipse installation structure. In particular,
     the native uninstallers will, by default, remove plug-in files that were
-   installed using the native installer without regard to these plug-ins being
+    installed using the native installer without regard to these plug-ins
-   needed by other features. As a result, features installed using native installers
+ being    needed by other features. As a result, features installed using
-     must be written into private product-specific installation location and
+ native installers     must be written into private product-specific installation
-   not  the shared Eclipse installation location. The shared Eclipse is made
+ location and   not  the shared Eclipse installation location. The shared
-   aware  of the produce-specific location via an installed "link file". <li>
+ Eclipse is made   aware  of the produce-specific location via an installed
-           <b>custom  install handling</b></li>
+ "link file". <li>           <b>custom  install handling</b></li>
                <br>
              In many cases the standard installation handling supplied by
- Eclipse     is  not be sufficient to handle various custom requirements.
+ Eclipse     is  not be sufficient to handle various custom requirements. To
- To accommodate     this,  R2.0 Eclipse supports custom install handlers packaged
+ accommodate     this,  R2.0 Eclipse supports custom install handlers packaged
  as part of   the feature  and executed during the feature installation. <li>
      <b>path  naming   conventions</b></li>
                <br>
              R1.0 mandated the use of the various identifiers and versions
  inside    the   packaged archives (eg. directory path names for plug-ins).
- This approach     has proven to be ackward and error prone. In 2.0, the packaging
+  This approach     has proven to be ackward and error prone. In 2.0, the
-  requirements     no longer mandate that path names of packaged files precisely
+ packaging  requirements     no longer mandate that path names of packaged
-  reflect the    contained identifiers and versions. The properly identified
+ files precisely  reflect the    contained identifiers and versions. The properly
-  install subdirectories    are created by the Eclipse support during the
+ identified  install subdirectories    are created by the Eclipse support
- installation  and update process     based on the archive content (rather
+ during the installation  and update process     based on the archive content
- than explicit  jar path structure set    up at packaging time)
+ (rather than explicit  jar path structure set    up at packaging time)
  </ul>
-Line 277
+Line 285
   of  execution     recognized by the Eclipse runtime environment. In general,
   plug-ins are   not exposed to users that select function during installation
   or update.  The reason is that plug-in boundaries are established by developers
-  for development    reasons (like function reuse) and present the wrong level
+   for development    reasons (like function reuse) and present the wrong
-  of granularity   in terms of what the user sees as the unit of function.
+ level   of granularity   in terms of what the user sees as the unit of function.
  <p>While plug-ins are being developed (ie. are frequently being changed),
        their internal file structure will reflect what is convenient to the
-  developer.     This will generally depend on the particular development tool
+   developer.     This will generally depend on the particular development
-  being used.     Typically, however, the developer will likely setup the
+ tool  being used.     Typically, however, the developer will likely setup
- plug-in  to execute     from a directory tree containing exposed .class files,
+ the plug-in  to execute     from a directory tree containing exposed .class
- rather  than executing     from a .jar (requires an extra step to create
+ files, rather  than executing     from a .jar (requires an extra step to
- the .jar  and we all know  developers  hate extra steps). Also, at this stage
+ create the .jar  and we all know  developers  hate extra steps). Also, at
- the developer  does not  pay particular  attention to plug-in versioning
+ this stage the developer  does not  pay particular  attention to plug-in
- information, because  the plug-in is continually  changing. </p>
+ versioning information, because  the plug-in is continually  changing. </p>
  <p>However, when the plug-in is ready to be packaged, it needs to be converted
        to a form suitable for packaging and installation. Typically it means
-Line 300
+Line 308
  <p><b>Plug-in Fragment</b> <br>
              Plug-in Fragments (or simply Fragments) allow independent packaging
-    of  certain  aspects of the base plug-in. This includes (but may not be
+     of  certain  aspects of the base plug-in. This includes (but may not
-  limited   to) translated  resources for the plug-in, OS-specific or windowing-system-specific
+ be   limited   to) translated  resources for the plug-in, OS-specific or
-      code.  At runtime, fragments are logically merged into the base plug-in.
+ windowing-system-specific      code.  At runtime, fragments are logically
-     From a packaging point of view, the install and update support does not
+ merged into the base plug-in.     From a packaging point of view, the install
-   really   differentiate  between plug-ins and their related fragments. </p>
+ and update support does not   really   differentiate  between plug-ins and
+ their related fragments. </p>
  <p><b>Feature</b> <br>
              A feature is an installation packaging mechanism used to define
   a  group    of versioned plug-ins and/or plug-in fragments plus non-plug-in
-  files that    is used to deliver some user function. A feature can also include
+   files that    is used to deliver some user function. A feature can also
-   other  features.  Features are exposed to users as part of the packaging
+ include   other  features.  Features are exposed to users as part of the
-  and installation   process,  because they represent a unit of function selection.
+ packaging  and installation   process,  because they represent a unit of
-   Features also  represent  a unit of installation. Features carry a version
+ function selection.   Features also  represent  a unit of installation. Features
-   identifier.</p>
+ carry a version   identifier.</p>
  <p>Features are packaged as a feature archive, referencing the required plug-ins,
        plug-in fragments and optional non-plug-in files. The feature archives
-    are   placed on an update server for download and installation by the
+    are   placed on an update server for download and installation by the Eclipse
- Eclipse     update  manager, or they can be used as the input into a formal
+     update  manager, or they can be used as the input into a formal packaging
- packaging     process  using one of the "traditional" installer technologies.
+     process  using one of the "traditional" installer technologies. The format
- The format     of the feature archive is described later. </p>
+     of the feature archive is described later. </p>
  <h3> <a name="Framework"></a> Framework</h3>
               The 2.0 installation and update support is provided as a framework
-Line 332
+Line 341
   feature   types   are  registere via the "org.eclipse.update.featureTypes"
   extension   point.</li>
                <li> concrete implementations of site (ISite interface) that
-  can   be  used  to support alternate site layout, or site behavior. New
+  can   be  used  to support alternate site layout, or site behavior. New concrete
- concrete    site  types   are registered via the "org.eclipse.update.siteTypes"
+    site  types   are registered via the "org.eclipse.update.siteTypes" extension
- extension    point.</li>
+    point.</li>
-               <li> each feature can specify a custom install handler as part
+                <li> each feature can specify a custom install handler as
-   of  its   feature  manifest. Install handlers (IInstallHandler interface)
+ part   of  its   feature  manifest. Install handlers (IInstallHandler interface)
    are  dynamically   invoked as part of the installation process to handle
-  non-plugin  data, plus   perform other custom processing allowed by the
+  non-plugin  data, plus   perform other custom processing allowed by the framework.</li>
- framework.</li>
  </ul>
               Eclipse provides default implementations of feature and site.
-Line 350
+Line 358
                  <tr>
               <td><b>Note: <i>The reminder of this document describes the
  default     concrete   implementation of the framework delivered with Eclipse.
- It specifies    the  structure of the default feature implementation, as
+ It specifies    the  structure of the default feature implementation, as well
- well as the default    site  implementation, plus the corresponding xml files
+ as the default    site  implementation, plus the corresponding xml files (feature.xml
- (feature.xml and  site.xml).   Providers of alternate concrete implementations
+ and  site.xml).   Providers of alternate concrete implementations can extend&nbsp;
- can extend&nbsp;  parts or   all of the default Eclipse implementation. This
+  parts or   all of the default Eclipse implementation. This includes providing
- includes providing  a mechanism   for dynamic computation of the site map
+  a mechanism   for dynamic computation of the site map (site.xml)</i></b></td>
- (site.xml)</i></b></td>
               </tr>
    </tbody>
-Line 382
+Line 389
  (see next    section) and non-plug-in files.
  <p>Features are identified using a structured identifier based on the provider
        internet domain name. For example, organization eclipse.org may produce
-     feature org.eclipse.javatooling. The character set used for feature identifiers
+      feature org.eclipse.javatooling. The character set used for feature
-     is as specified for plug-in identifiers (see reference information describing
+ identifiers      is as specified for plug-in identifiers (see reference information
-       the plug-in manifest). </p>
+ describing        the plug-in manifest). </p>
  <p>The recommended convention for naming the feature archives is <br>
              <tt>&lt;id&gt;_&lt;version&gt;.jar</tt> </p>
  <p>Where <tt>&lt;id&gt;</tt> is the feature identifier and <tt>&lt;version&gt;</tt>
         is the full version identifier contained in the respective feature.xml.
-      Note that this is a recommended convention that minimizes chance of collisions,
+       Note that this is a recommended convention that minimizes chance of
-       but is not required by the Eclipse architecture. For example, the following
+ collisions,       but is not required by the Eclipse architecture. For example,
-       are valid feature archive names </p>
+ the following       are valid feature archive names </p>
  <p><tt>org.eclipse.javatooling_1.0.3.jar</tt> <br>
              <tt>org.eclipse.pde_2.0.jar</tt> <br>
-Line 415
+Line 422
  <p><tt>&lt;?xml encoding="ISO-8859-1"?&gt;</tt> </p>
- <p><tt>&lt;!ELEMENT feature (install-handler?, description?, copyright?, license?,
+ <p><tt>&lt;!ELEMENT feature (install-handler?, description?, copyright?,
- url?, includes*, requires?, plugin*, data*)&gt;</tt> <br>
+ license?, url?, includes*, requires?, plugin*, data*)&gt;</tt> <br>
              <tt>&lt;!ATTLIST feature</tt> <br>
              <tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        CDATA #REQUIRED</tt> <br>
-Line 487
+Line 494
        CDATA #REQUIRED</tt> <br>
              <tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        CDATA #IMPLIED</tt> <br>
-             <tt>&gt;</tt> </p>
+   <tt>&nbsp;&nbsp;&nbsp; type &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+    &nbsp;(update|web) "update"</tt><tt><br>
+   &gt;</tt> </p>
+ <p> </p>
  <p><tt>&lt;!ELEMENT includes EMPTY&gt;</tt> <br>
              <tt>&lt;!ATTLIST includes</tt> <br>
-Line 578
+Line 588
                <li> os - optional operating system specification. A comma-separated
       list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this feature should only be installed on one of the specified
-       os systems. If this attribute is not specified, the feature can be installed
+        os systems. If this attribute is not specified, the feature can be
-       on all systems (portable implementation). This information is used
+ installed       on all systems (portable implementation). This information
- as   a  hint by the installation and update support (user can force installation
+ is used as   a  hint by the installation and update support (user can force
-    of feature regardless of this setting).</li>
+ installation    of feature regardless of this setting).</li>
                <li> arch - optional machine architecture specification. A
  comma-separated       list of architecture designators defined by Eclipse
- (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>.
+ (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates
- Indicates this feature   should only    be installed on one of the specified
+ this feature   should only    be installed on one of the specified systems.
- systems. If this attribute   is not specified,   the feature can be installed
+ If this attribute   is not specified,   the feature can be installed on all
- on all systems (portable   implementation).  This   information is used as
+ systems (portable   implementation).  This   information is used as a hint
- a hint by the installation   and update support  (user   can force installation
+ by the installation   and update support  (user   can force installation of
- of feature regardless  of this setting).</li>
+ feature regardless  of this setting).</li>
                <li> ws - optional windowing system specification. A comma-separated
       list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this feature should only be installed on one of the specified
-       ws systems. If this attribute is not specified, the feature can be installed
+        ws systems. If this attribute is not specified, the feature can be
-       on all systems (portable implementation). This information is used
+ installed       on all systems (portable implementation). This information
- as   a  hint by the installation and update support (user can force installation
+ is used as   a  hint by the installation and update support (user can force
-    of feature regardless of this setting).</li>
+ installation    of feature regardless of this setting).</li>
                <li> nl - optional locale specification. A comma-separated
  list   of  locale   designators defined by Java. Indicates this feature should
- only  be installed   on a system running with a compatible locale (using Java
+  only  be installed   on a system running with a compatible locale (using
- locale-matching    rules). If this attribute is not specified, the feature
+ Java locale-matching    rules). If this attribute is not specified, the feature
    can be installed   on all systems (language-neutral implementation). This
-   information is used   as a hint by the installation and update support
+   information is used   as a hint by the installation and update support (user
- (user   can force installation    of feature regardless of this setting).</li>
+   can force installation    of feature regardless of this setting).</li>
                <li> colocation-affinity - optional reference to another feature
     identifier    used to select the default installation location for this
   feature.  When  this feature is being installed as a new feature (no other
-Line 614
+Line 624
  . Default     if        <i>false</i> (not a primary feature).</li>
                <li> application - optional identifier of the Eclipse application
     that   is to be used during startup when the declaring feature is the
-      <a href="#Dominant_Feature"> primary feature</a> . The application identifier
+       <a href="#Dominant_Feature"> primary feature</a> . The application
-      must represent a valid application registered in the <tt>org.eclipse.core.runtime.applications</tt>
+ identifier      must represent a valid application registered in the <tt>org.eclipse.core.runtime.applications</tt>
       extension point. Default is <tt>org.eclipse.ui.workbench</tt>.</li>
-       <li> plugin- optional identifier of the primary plugin associated with
+        <li> plugin- optional identifier of the primary plugin associated
-  this <a
+ with  this <a
   href="file:///C:/OTI/workspace/plugins/platform-update-home/doc/eclipse_update_packaging.html#Dominant_Feature">primary
   feature</a>. The primary plugin carries branding information. If the plugin
   attribute is not declared, the primary plugin identifier used will be the
-Line 640
+Line 650
  interpreted  as  a fully qualified  name of a class contained in the specified
        <i>library</i>.     If       <i>library</i>   is not specified, the
  value is is interpreted   as  an extension identifier  of an extension registered
- in the <i>org.eclipse.update.installHandlers</i>        extension point.
+ in the <i>org.eclipse.update.installHandlers</i>        extension point. In
- In either case, the resulting class must implement  the          <i> IInstallHandler</i>
+ either case, the resulting class must implement  the          <i> IInstallHandler</i>
  interface. The class is dynamically loaded   and called at specific points
  during feature processing. The handler has  visibility to the API classes
  from the update plug-in, and Eclipse plug-ins    required by the update plugin.</li>
    </ul>
-               <li> &lt;description&gt; - brief component description as simple
+                <li> &lt;description&gt; - brief component description as
-    text.    Intended to be translated.</li>
+ simple    text.    Intended to be translated.</li>
    <ul>
               <li> url - optional URL for the full description as HTML. The
   URL   can   be  specified as absolute of relative. If relative, it is assumed
   to  be relative   to (and packaged in) the feature archive. Note, that for
-  NL  handling the  URL value should be separated to allow alternate URLs
+  NL  handling the  URL value should be separated to allow alternate URLs to
- to  be  specified for  each national language. &nbsp;URL support keywords
+  be  specified for  each national language. &nbsp;URL support keywords $os$,$ws$,$arch$
- $os$,$ws$,$arch$  and $nl$ that will be replaced by the appropriate operating
+  and $nl$ that will be replaced by the appropriate operating system, windowing
- system, windowing  system, operating architecture or national language value.</li>
+  system, operating architecture or national language value.</li>
    </ul>
                <li> &lt;copyright&gt; - feature copyright as simple text.
-Line 667
+Line 677
               <li> url - optional URL for the full description as HTML. The
   URL   can   be  specified as absolute of relative. If relative, it is assumed
   to  be relative   to (and packaged in) the feature archive. Note, that for
-  NL  handling the  URL value should be separated to allow alternate URLs
+  NL  handling the  URL value should be separated to allow alternate URLs to
- to  be  specified for  each national language. URL support keywords $os$,$ws$,$arch$
+  be  specified for  each national language. URL support keywords $os$,$ws$,$arch$
   and $nl$ that will be replaced by the appropriate operating system, windowing
   system, operating architecture or national language value.</li>
    </ul>
-               <li> &lt;license&gt; - feature "click-through" license as simple
+                <li> &lt;license&gt; - feature "click-through" license as
-    text.    Intended to be translated. It is displayed in a standard dialog
+ simple    text.    Intended to be translated. It is displayed in a standard
-   with [Accept]    [Reject] actions during the download/ installation process.
+ dialog   with [Accept]    [Reject] actions during the download/ installation
-   Note, that click-through   license must be specified for any feature that
+ process.   Note, that click-through   license must be specified for any feature
-   will be selected for installation   or update using the Eclipse update
+ that   will be selected for installation   or update using the Eclipse update
- manager.    When using nested features, only the nesting parent (ie. the
+ manager.    When using nested features, only the nesting parent (ie. the feature
- feature selected    for installation or update) must have click-through license
+ selected    for installation or update) must have click-through license text
- text defined.    The license text is required even if the optional <i>url</i>
+ defined.    The license text is required even if the optional <i>url</i> attribute
- attribute is   specified.</li>
+ is   specified.</li>
    <ul>
               <li> url - optional URL for the full description as HTML. The
   URL   can   be  specified as absolute of relative. If relative, it is assumed
   to  be relative   to (and packaged in) the feature archive. Note, that for
-  NL  handling the  URL value should be separated to allow alternate URLs
+  NL  handling the  URL value should be separated to allow alternate URLs to
- to  be  specified for  each national language. Note, that the "content" of
+  be  specified for  each national language. Note, that the "content" of this
- this  URL  is <b>not</b>    what is presented as the click-through license
+  URL  is <b>not</b>    what is presented as the click-through license during
- during  installation  processing.    The click-through license is the actual
+  installation  processing.    The click-through license is the actual value
- value  of the <i>&lt;license&gt;</i>      element (eg. <tt>&lt;license&gt;click
+  of the <i>&lt;license&gt;</i>      element (eg. <tt>&lt;license&gt;click
  through text&lt;/license&gt;</tt>).&nbsp;URL support keywords $os$,$ws$,$arch$
  and $nl$ that will be replaced by the appropriate operating system, windowing
   system, operating architecture or national language value.</li>
-Line 708
+Line 718
               <li> url - actual URL</li>
                <li> label - displayable label (name) for the referenced site</li>
      </ul>
                <li> &lt;discovery&gt; - URL to go to for new features. In
  general,     a  provider  can use this element to reference its own site(s),
-Line 718
+Line 729
      <ul>
               <li> url - actual URL</li>
                <li> label - displayable label (name) for the referenced site</li>
+       <li>type - whether the site is an regular update site or a web site.
+  The web site may be a web-triggered-install web site. (<tt>update</tt> is
+ the default)<br>
+       </li>
      </ul>
    </ul>
                <li> &lt;includes&gt; - optional reference to a nested feature
-   that   is  considered to be part of this feature. Nested features must
+   that   is  considered to be part of this feature. Nested features must be
- be   located   on  the same update site as this feature</li>
+   located   on  the same update site as this feature</li>
    <ul>
               <li> id - required nested feature identifier</li>
-Line 735
+Line 751
  included     feature  can be optionally installed. Default is "false"<br>
                  </li>
                  <li>match&nbsp; - optional rule that will be applied when
- resolving      the feature reference. A <samp>perfect</samp> match (the default
+  resolving      the feature reference. A <samp>perfect</samp> match (the
- that  matches    the 2.0.1 behavior) requires that the feature has exactly
+ default  that  matches    the 2.0.1 behavior) requires that the feature has
- the version specified    by the version attribute. Other choices progressively
+ exactly  the version specified    by the version attribute. Other choices
- relax the rule (<samp>    equivalent</samp> allows only service part of the
+ progressively  relax the rule (<samp>    equivalent</samp> allows only service
- version to be more recent,          <samp>compatible</samp> also allows minor
+ part of the  version to be more recent,          <samp>compatible</samp>
- part to be included in the   consideration, while <samp>greaterOrEqual</samp>
+ also allows minor  part to be included in the   consideration, while <samp>greaterOrEqual</samp>
     simply allows any version   that is more recent or identical to the one
   specified).</li>
-                 <li>search-location&nbsp; - optional. Indicates whether the
+                  <li>search-location&nbsp; - optional. Indicates whether
-  "New   Updates"   action should search the update location determined by
+ the   "New   Updates"   action should search the update location determined
- the nesting   root feature  (<tt>root</tt>, is the default), or the location
+ by  the nesting   root feature  (<tt>root</tt>, is the default), or the location
  defined by   the nested feature  (<tt>self</tt>), or search both (<tt>both</tt>)
    in that   order (root first,  self if nothing is found).</li>
-Line 765
+Line 781
   and   feature   are specified, plugin takes precedence upon feature. Feature
   or   plugin must   be specified.</li>
                <li> version - optional plug-in/feature version specification</li>
-                   <li>patch - optional specification indicating if this feature
+                    <li>patch - optional specification indicating if this
-    is  a  patch of the dependant feature. Default is "false". If patch is
+ feature     is  a  patch of the dependant feature. Default is "false". If
- true,   version  must be specified. If patch is true, only feature must be
+ patch is  true,   version  must be specified. If patch is true, only feature
- specified.   If patch  is true, and match is specified, it must be 'perfect'.<br>
+ must be  specified.   If patch  is true, and match is specified, it must
+ be 'perfect'.<br>
                    </li>
                <li> match - optional matching rule. Valid values and processing
     are   as  follows:</li>
-Line 784
+Line 801
                      </li>
                <li> <b><i>perfect</i></b> - dependent plug-in version must
  match    exactly   the specified version.</li>
-               <li> <b><i>equivalent</i></b> - dependent plug-in version must
+                <li> <b><i>equivalent</i></b> - dependent plug-in version
-   be  at  least  at the version specified, or at a higher service level (major
+ must   be  at  least  at the version specified, or at a higher service level
-   and minor version  levels must equal the specified version).</li>
+ (major    and minor version  levels must equal the specified version).</li>
-               <li> <b><i>compatible</i></b> - dependent plug-in version must
+                <li> <b><i>compatible</i></b> - dependent plug-in version
-   be  at  least  at the version specified, or at a higher service level or
+ must   be  at  least  at the version specified, or at a higher service level
-  minor  level  (major  version level must equal the specified version).</li>
+ or  minor  level  (major  version level must equal the specified version).</li>
                <li> <b><i>greaterOrEqual</i></b> - dependent plug-in version
   must   be  at least at the version specified, or at a higher service, minor
   or major   level.</li>
-Line 797
+Line 814
        </ul>
      </ul>
    </ul>
-Line 805
+Line 823
    <ul>
               <li> id - required plug-in identifier (from plugin.xml)</li>
                <li> version - required plug-in version (from plugin.xml)</li>
-               <li> fragment - optional specification indicating if this entry
+                <li> fragment - optional specification indicating if this
-   is  a  plug-in  fragment. Default is "false"</li>
+ entry    is  a  plug-in  fragment. Default is "false"</li>
                <li> os - optional operating system specification. A comma-separated
       list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this entry should only be installed on one of the specified
      os  systems. If this attribute is not specified, the entry can be installed
-      on all systems (portable implementation). This information is used as
+       on all systems (portable implementation). This information is used
-  a  hint  by the installation and update support (user can force installation
+ as   a  hint  by the installation and update support (user can force installation
     of entry  regardless of this setting).</li>
                <li> arch - optional machine architecture specification. A
  comma-separated       list of architecture designators defined by Eclipse
- (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>.
+ (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates
- Indicates this feature   should only    be installed on one of the specified
+ this feature   should only    be installed on one of the specified systems.
- systems. If this attribute   is not specified,   the feature can be installed
+ If this attribute   is not specified,   the feature can be installed on all
- on all systems (portable   implementation).  This   information is used as
+ systems (portable   implementation).  This   information is used as a hint
- a hint by the installation   and update support  (user   can force installation
+ by the installation   and update support  (user   can force installation of
- of feature regardless  of this setting).</li>
+ feature regardless  of this setting).</li>
                <li> ws - optional windowing system specification. A comma-separated
       list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this entry should only be installed on one of the specified
      ws  systems. If this attribute is not specified, the entry can be installed
-      on all systems (portable implementation). This information is used as
+       on all systems (portable implementation). This information is used
-  a  hint  by the installation and update support (user can force installation
+ as   a  hint  by the installation and update support (user can force installation
     of entry  regardless of this setting).</li>
                <li> nl - optional locale specification. A comma-separated
  list   of  locale   designators defined by Java. Indicates this entry should
-Line 837
+Line 855
  information  is used as  a hint by the installation and update support (user
  can force  installation   of entry regardless of this setting).</li>
                <li> download-size - optional hint supplied by the feature
- packager,      indicating  the download size in KBytes of the referenced
+ packager,      indicating  the download size in KBytes of the referenced plug-in
+ archive.The size should not contain decimal.     If not specified,  the download
+ size is not known (<b>Implementation Note:</b>     the implementation  needs
+ to distinguish between "not known" and 0 size)</li>
+                <li> install-size - optional hint supplied by the feature
+ packager,      indicating   the install size in KBytes of the referenced
  plug-in archive.The size should not contain decimal.     If not specified,
-  the download size is not known (<b>Implementation Note:</b>     the implementation
+   the install size is not known (<b>Implementation Note:</b>     the implementation
   needs to distinguish between "not known" and 0 size)</li>
-               <li> install-size - optional hint supplied by the feature packager,
-     indicating   the install size in KBytes of the referenced plug-in archive.
-     The size should not contain decimal. If not specified,   the install size
- is not known (<b>Implementation Note:</b>     the implementation   needs to
- distinguish between "not known" and 0 size)</li>
    </ul>
-               <li> &lt;data&gt; - identifies non-plugin and non-feature data
+                <li> &lt;data&gt; - identifies non-plugin and non-feature
-   that  is part of the feature. Generally, data are post-install processed
+ data   that  is part of the feature. Generally, data are post-install processed
   using feature Install handler. Feature files like feature.properties are
  not considered  data.</li>
-Line 860
+Line 878
       list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this entry should only be installed on one of the specified
      os  systems. If this attribute is not specified, the entry can be installed
-      on all systems (portable implementation). This information is used as
+       on all systems (portable implementation). This information is used
-  a  hint  by the installation and update support (user can force installation
+ as   a  hint  by the installation and update support (user can force installation
     of entry  regardless of this setting).</li>
                <li> arch - optional machine architecture specification. A
  comma-separated       list of architecture designators defined by Eclipse
- (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>.
+ (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates
- Indicates this feature   should only    be installed on one of the specified
+ this feature   should only    be installed on one of the specified systems.
- systems. If this attribute   is not specified,   the feature can be installed
+ If this attribute   is not specified,   the feature can be installed on all
- on all systems (portable   implementation).  This   information is used as
+ systems (portable   implementation).  This   information is used as a hint
- a hint by the installation   and update support  (user   can force installation
+ by the installation   and update support  (user   can force installation of
- of feature regardless  of this setting).</li>
+ feature regardless  of this setting).</li>
                <li> ws - optional windowing system specification. A comma-separated
       list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this entry should only be installed on one of the specified
      ws  systems. If this attribute is not specified, the entry can be installed
-      on all systems (portable implementation). This information is used as
+       on all systems (portable implementation). This information is used
-  a  hint  by the installation and update support (user can force installation
+ as   a  hint  by the installation and update support (user can force installation
     of entry  regardless of this setting).</li>
                <li> nl - optional locale specification. A comma-separated
  list   of  locale   designators defined by Java. Indicates this entry should
-Line 886
+Line 904
  information  is used as  a hint by the installation and update support (user
  can force  installation   of entry regardless of this setting).</li>
                <li> download-size - optional hint supplied by the feature
- packager,      indicating  the download size in KBytes of the referenced
+ packager,      indicating  the download size in KBytes of the referenced data
- data archive.    If  not specified,  the download size is not known (<b>Implementation
+ archive.    If  not specified,  the download size is not known (<b>Implementation
+ Note:</b>      the implementation  needs to distinguish between "not known"
+ and 0 size)</li>
+                <li> install-size - optional hint supplied by the feature
+ packager,      indicating   the install size in KBytes of the referenced
+ data archive.    If  not specified,   the install size is not known (<b>Implementation
  Note:</b>      the implementation  needs to distinguish between "not known"
  and 0 size)</li>
-               <li> install-size - optional hint supplied by the feature packager,
-     indicating   the install size in KBytes of the referenced data archive.
-   If  not specified,   the install size is not known (<b>Implementation Note:</b>
-     the implementation   needs to distinguish between "not known" and 0 size)</li>
    </ul>
-Line 942
+Line 961
              <tt>org.eclipse.ui.nl_2.0.jar</tt> <br>
              <tt>my_plugin.jar</tt> </p>
- <p>Internally, each plug-in archive packages all the relevant plug-in or fragment
+ <p>Internally, each plug-in archive packages all the relevant plug-in or
- files relative to its plug-in or fragment directory (but not including the
+ fragment files relative to its plug-in or fragment directory (but not including
- directory path element). The archive has the following structure </p>
+ the directory path element). The archive has the following structure </p>
  <p><tt>plugin.xml *OR* fragment.xml</tt> <br>
              <tt>other plug-in or feature files and subdirectories</tt> <br>
-Line 956
+Line 975
               In Eclipse, translated plug-in information is packaged either
   together     with the base plug-in, or as a plug-in fragment. At runtime,
   Eclipse locates     the translations for the required locale. The use of
- fragments allows translations     to be added to the runtime without the
+ fragments allows translations     to be added to the runtime without the need
- need to repackage the base plug-ins.
+ to repackage the base plug-ins.
  <p>This mechanism cannot be used for translating the actual packaging information
        that is part of the installation xml files. Consequently the standard
    Java    translation conventions are used for the packaging information,
-Line 966
+Line 985
  <h4> <a name="Translated_Feature_Information"></a> Translated Feature Information</h4>
               <b>Note:</b> This section describes the conventions used for
- translating       the information contained within the feature manifest. It
+  translating       the information contained within the feature manifest.
- allows for  the    update client to select the correctly localized strings
+ It allows for  the    update client to select the correctly localized strings
- from the update    server.  This section specifically does not describe localization
+  from the update    server.  This section specifically does not describe
- of individual    plug-ins.
+ localization  of individual    plug-ins.
  <p>Several of the attributes within the feature manifest are strings intended
        for display through user interfaces. To facilitate translation, these
    attribute    values use the convention defined for translatable attributes
-Line 1001
+Line 1020
       </p>
  <p>The resulting resource bundle can be used in <tt>IPluginDescriptor.getResourceString(String,ResourceBundle)</tt>
-        to actually return the correct translated string for the manifest
+        to actually return the correct translated string for the manifest attribute.
- attribute.       </p>
+       </p>
  <h4> <a name="Translated_Plug-In_Information"></a> Translated Plug-In Information</h4>
               No change from 1.0. Translated plug-in information should be
-Line 1017
+Line 1036
  eclipse.org       development resources page of the Update component.
  <h3> <a name="Packaging_Non_Plug_In_Files"></a> Packaging Non-Plug-In Files</h3>
-              Arbitrary non-plug-in files can be included as part of the feature
+               Arbitrary non-plug-in files can be included as part of the
-    definition    using the <tt>&lt;data&gt;</tt> elements. Non-plug-in files
+ feature     definition    using the <tt>&lt;data&gt;</tt> elements. Non-plug-in
-    typically also    requires specification of a custom install handler. In
+ files     typically also    requires specification of a custom install handler.
-   general, the Eclipse    support only downloads the referenced non-plug-in
+ In   general, the Eclipse    support only downloads the referenced non-plug-in
    files and calls the custom    install handler to perform any actual installation
    steps.
  <p>Eclipse does not specify the format of the non-plug-in files. </p>
-Line 1030
+Line 1049
  packaged     as  part of the <a href="#Feature_Archive">feature archive</a>
  . The installer      must implement the <tt>IInstallHandler</tt> interface
  (in most cases will     extend the <tt>BaseInstallHandler</tt> abstract helper
- class which implements     <tt>IInstallHandler</tt>). When required, the install
+  class which implements     <tt>IInstallHandler</tt>). When required, the
- handler is dynamically     loaded by the installation and update code, and
+ install handler is dynamically     loaded by the installation and update
- is called at specific points    during its processing. The install handler
+ code, and is called at specific points    during its processing. The install
- code has visibility to classes    from the installation and update support
+ handler code has visibility to classes    from the installation and update
- plug-in, and its prerequisite  plug-ins.
+ support plug-in, and its prerequisite  plug-ins.
- <p><b>Implementation Note:</b> the detailed list of visible prerequisite plug-ins
+ <p><b>Implementation Note:</b> the detailed list of visible prerequisite
- is still evolving. It is expected to include <tt>org.eclipse.core.boot </tt>
+ plug-ins is still evolving. It is expected to include <tt>org.eclipse.core.boot
- and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt>
+ </tt> and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt>
         and <tt>org.eclipse.swt</tt> when running with full workbench (ie.
  not    "headless  mode"). Also, it would be useful to always expose <tt>org.eclipse.core.ant</tt>
         so that build scripts can be used as part of the install handler implementation.
        </p>
  <p>The IInstallHandler interface supports the following methods [<b>Implementation
-       Note:</b> the detailed definition of the IInstallHandler interface is
+        Note:</b> the detailed definition of the IInstallHandler interface
-   still    evolving. The description below is not an API specification (simply
+ is   still    evolving. The description below is not an API specification
-   a functional    description)]: </p>
+ (simply   a functional    description)]: </p>
  <ul>
               <li> install-initiated - the install handler is called after
- a  feature     was selected for installation, but before any files were downloaded.
+  a  feature     was selected for installation, but before any files were
-  It   is  intended  to implement any custom click-through or user registration
+ downloaded.   It   is  intended  to implement any custom click-through or
-   dialogs.  The base implementation of this method supplied with the abstract
+ user registration    dialogs.  The base implementation of this method supplied
-   class     <tt>BaseInstallHandler       </tt>performs the default click-through
+ with the abstract    class     <tt>BaseInstallHandler       </tt>performs
-   processing using the license  text supplied as part of the feature manifest.
+ the default click-through    processing using the license  text supplied
-   On return this method indicates  success (installation continues) of failure
+ as part of the feature manifest.    On return this method indicates  success
-   (installation is aborted).</li>
+ (installation continues) of failure    (installation is aborted).</li>
                <li> install-downloaded - the install handler is called after
-  all   the   required  feature files were downloaded (feature, plugins, data)
+   all   the   required  feature files were downloaded (feature, plugins,
-  but   before   the actual  installation is performed. The install handler
+ data)   but   before   the actual  installation is performed. The install
-  is expected   to   perform verification  of the non-plug-in data files (eg.
+ handler   is expected   to   perform verification  of the non-plug-in data
-  security),  or any   other pre-install processing.&nbsp; On return this method
+ files (eg.   security),  or any   other pre-install processing.&nbsp; On
-  indicates   success   (installation continues) or failure (installation is
+ return this method  indicates   success   (installation continues) or failure
-  aborted).</li>
+ (installation is  aborted).</li>
                <li> install-completion - the install handler is called after
   the   feature   information and the plug-ins were installed. It is expected
-  to  complete the  installation of any non-plug-in data that was part of the
+   to  complete the  installation of any non-plug-in data that was part of
-  feature.  On return  this method indicates success (returns custom install
+ the  feature.  On return  this method indicates success (returns custom install
   log) or failure (installation  is aborted). On failure, the install handler
   is expected to perform any required cleanup.</li>
                <li> uninstall-initiated - the install handler is called when
   a  feature    is selected for removal, but before any of the standard uninstall
    processing    has taken place. It is passed the custom install log created
    by the install    handler install-completion step.</li>
-               <li> uninstall-completion - the install handler is called on
+                <li> uninstall-completion - the install handler is called
-  completion      of the standard uninstall steps. It is passed the custom
+ on  completion      of the standard uninstall steps. It is passed the custom
  install log created     by the install handler install-completion step.</li>
  </ul>
               Note, that as a general practice, install handlers should be
- provided     in  their own jars (even though they could be just exposed in
+  provided     in  their own jars (even though they could be just exposed
- the feature     archive  jar). The jar should be signed, and sealed.
+ in  the feature     archive  jar). The jar should be signed, and sealed.
  <h3> <a name="Security_Considerations"></a> Security Considerations</h3>
               The general approach is to use base Java jar signing for the
-Line 1196
+Line 1215
   to  a  type   string registered via the <a href="#Framework">install framework</a>
       extension  point. If not specified, the type is assumed to be the default
      Eclipse site  type (as specified in this document).</li>
-               <li> url - optional URL defining the update site baseline URL
+                <li> url - optional URL defining the update site baseline
-  (used    to  determine individual &lt;feature&gt; and &lt;archive&gt; location).&nbsp;
+ URL   (used    to  determine individual &lt;feature&gt; and &lt;archive&gt;
-       Can be relative or absolute. If relative, is relative to site.xml.
+ location).&nbsp;       Can be relative or absolute. If relative, is relative
- If   not    specified, the default is the URL location of the site.xml file.</li>
+ to site.xml. If   not    specified, the default is the URL location of the
+ site.xml file.</li>
    </ul>
                <li> &lt;description&gt; - brief description as simple text.
-Line 1217
+Line 1237
                <li> &lt;feature&gt; - identifies referenced feature archive</li>
    <ul>
-              <li> type - optional feature type specification. The value refers
+               <li> type - optional feature type specification. The value
-    to  a  type  string registered via the <a href="#Framework">install framework</a>
+ refers    to  a  type  string registered via the <a href="#Framework">install
-        extension point. If not specified, the type is assumed to be the default
+ framework</a>        extension point. If not specified, the type is assumed
-       feature type for the site. If the site type is the default Eclipse
+ to be the default       feature type for the site. If the site type is the
- site     type,  the default feature type is the packaged feature type (as
+ default Eclipse site     type,  the default feature type is the packaged
- specified     in this  document).</li>
+ feature type (as specified     in this  document).</li>
-               <li> id - optional feature identifier. The information is used
+                <li> id - optional feature identifier. The information is
-   as  a  performance   optimization to speed up searches for features. Must
+ used   as  a  performance   optimization to speed up searches for features.
-   match  the identifier   specified in the feature.xml of the referenced
+ Must   match  the identifier   specified in the feature.xml of the referenced
  archive   (the  url attribute).   If specified, the version attribute must
  also be  specified.</li>
                <li> version - optional feature version. The information is
  used   as  a  performance  optimization to speed up searches for features.
- Must  match  the  version specified in the feature.xml of the referenced archive
+  Must  match  the  version specified in the feature.xml of the referenced
-  (the url attribute).  If specified, the id attribute must also be specified.</li>
+ archive  (the url attribute).  If specified, the id attribute must also be
-               <li> url - required URL reference to the feature archive. Can
+ specified.</li>
-  be  relative    or absolute. If relative, it is relative to the location
+                <li> url - required URL reference to the feature archive.
+ Can   be  relative    or absolute. If relative, it is relative to the location
  of the  site.xml   file.       <b>Note</b>: the default site implementation
    allows  features  to be accessed without being explicitly declared using
   a &lt;feature&gt;  entry. By default, an undeclared features reference is
-Line 1246
+Line 1267
       list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this feature should only be installed on one of the specified
        os systems. If this attribute is "*", the feature can be installed
-  on   all systems (portable implementation). This information is used as a
- hint   by the installation and update support (user can force installation
-  of feature   regardless of this setting).</li>
-               <li> arch - optional machine architecture specification. A
- comma-separated       list of architecture designators defined by Eclipse
- (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>.
- Indicates this feature   should only    be installed on one of the specified
- systems. If this attribute&nbsp;is     "*",  the feature can be installed
  on all systems (portable implementation).     This  information is used as
  a hint by the installation and update support     (user  can force installation
  of feature regardless of this setting).</li>
+                <li> arch - optional machine architecture specification. A
+ comma-separated       list of architecture designators defined by Eclipse
+ (see Javadoc for        <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates
+ this feature   should only    be installed on one of the specified systems.
+ If this attribute&nbsp;is     "*",  the feature can be installed on all systems
+ (portable implementation).     This  information is used as a hint by the
+ installation and update support     (user  can force installation of feature
+ regardless of this setting).</li>
                <li> ws - optional windowing system specification. A comma-separated
       list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
        . Indicates this feature should only be installed on one of the specified
        ws systems. If this attribute&nbsp;is "*", the feature can be installed
-       on all systems (portable implementation). This information is used as
+        on all systems (portable implementation). This information is used
-   a  hint by the installation and update support (user can force installation
+ as   a  hint by the installation and update support (user can force installation
     of feature regardless of this setting).</li>
                <li> nl - optional locale specification. A comma-separated
  list   of  locale   designators defined by Java. Indicates this feature should
- only  be installed   on a system running with a compatible locale (using Java
+  only  be installed   on a system running with a compatible locale (using
- locale-matching    rules). If this attribute&nbsp;is "*", the feature can
+ Java locale-matching    rules). If this attribute&nbsp;is "*", the feature
- be installed on all  systems (language-neutral implementation). This information
+ can be installed on all  systems (language-neutral implementation). This
- is used as a hint by the installation and update support (user can force
+ information is used as a hint by the installation and update support (user
- installation  of feature regardless of this setting).</li>
+ can force installation  of feature regardless of this setting).</li>
                <li>patch - optional specification indicating if this feature
   is  a   patch. Default is "false".&nbsp;</li>
-Line 1287
+Line 1308
    <ul>
               <li> path - required archive path identifier. This is a string
   that   is  determined  by the <a
-  href="#Feature_Archive_Mapping_Id_To_Path">feature</a>      referencing this
+  href="#Feature_Archive_Mapping_Id_To_Path">feature</a>      referencing
- archive and is not otherwise interpreted by the site  (other   than as a
+ this archive and is not otherwise interpreted by the site  (other   than
- lookup token).</li>
+ as a lookup token).</li>
                <li> url - required URL reference to the archive. Can be relative
     or  absolute.  If relative, it is relative to the location of the site.xml
     file.</li>
-Line 1305
+Line 1326
                <li> label - displayable label. Intended to be translated.</li>
    </ul>
-               <li> &lt;category&gt; - actual category specification for a
+                <li> &lt;category&gt; - actual category specification for
- feature     entry</li>
+ a  feature     entry</li>
    <ul>
              name - category name
-Line 1319
+Line 1340
  <p>Translatable text contained in the site.xml can be separated into site&lt;_locale&gt;.properties
        files using Java property bundle conventions. Note that the translated
-    strings  are used at installation time (ie. do not employ the plug-in fragment
+     strings  are used at installation time (ie. do not employ the plug-in
-    runtime  mechanism). The property bundles are located relative to the
+ fragment    runtime  mechanism). The property bundles are located relative
- site.xml    location.   </p>
+ to the site.xml    location.   </p>
  <h3> <a name="Default_Site_Layout"></a> Default Site Layout</h3>
               <tt>&lt;site root&gt;/</tt> <br>
-Line 1347
+Line 1368
               <li> by supplying server-side logic on the update server (eg.
   implementing      servlets that compute the site.xml map, and control access
   to individual     archives based on some user criteria)</li>
-               <li> by supplying a custom concrete implementation of the site
+                <li> by supplying a custom concrete implementation of the
-   object    (installed  on the client machine, update server specified <tt>&lt;site
+ site   object    (installed  on the client machine, update server specified
-    type=""&gt;</tt>  ). The custom concrete site implementation, together
+     <tt>&lt;site     type=""&gt;</tt>  ). The custom concrete site implementation,
- with   any server-side   logic support the required control mechanisms.</li>
+ together  with   any server-side   logic support the required control mechanisms.</li>
  </ul>
               Eclipse provides an example demonstrating an implementation
-Line 1382
+Line 1403
              <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
       META_INF/</tt>   </p>
- <p><b>Implementation Note:</b> we will go back to the original design of not
+ <p><b>Implementation Note:</b> we will go back to the original design of
- splitting out fragments (ie. plugin and fragments go into the same install
+ not splitting out fragments (ie. plugin and fragments go into the same install
        location) </p>
  <h3> <a name="Unmanaged_Plugins"></a> "Unmanaged" Plug-Ins</h3>
-Line 1391
+Line 1412
   plug-ins     that were directly installed into the Eclipse file tree without
   being part    of a feature (eg. developer unzipping plug-in archive directly
   into the  Eclipse  file tree).
- <p>Eclipse runtime recognizes these plugins during startup and loads the plug-in
+ <p>Eclipse runtime recognizes these plugins during startup and loads the
- information into the runtime registry following the standard plug-in binding
+ plug-in information into the runtime registry following the standard plug-in
- rules. The update support also recognizes the presence of this new plug-in,
+ binding rules. The update support also recognizes the presence of this new
- but since this plug-in is not part of any feature it cannot be updated using
+ plug-in, but since this plug-in is not part of any feature it cannot be updated
- the update support (hence "unmanaged"). Unmanaged plug-in that become referenced
+ using the update support (hence "unmanaged"). Unmanaged plug-in that become
- by a feature as a result of some future installation or update action become
+ referenced by a feature as a result of some future installation or update
- "managed" (can be updated as part of the feature). </p>
+ action become "managed" (can be updated as part of the feature). </p>
  <p>Unmanaged plug-ins are not displayed as part of the installation and update
        UI. </p>
-Line 1405
+Line 1426
  <h3> <a name="Using_Native_Platform_Installers"></a> Using Native Platform
       Installers</h3>
               The Eclipse installation contains plugins that can be shared
- across    multiple   features. When installing and uninstalling features using
+  across    multiple   features. When installing and uninstalling features
- the   Eclipse installation   and update support, these relationship are correctly
+ using the   Eclipse installation   and update support, these relationship
-   maintained. Only one   copy of any version of a plug-in is used.
+ are correctly   maintained. Only one   copy of any version of a plug-in is
+ used.
  <p>However, when using native platform installers, performing native uninstall
-       creates problems because plug-ins would be removed without regard to
+        creates problems because plug-ins would be removed without regard
-  any    sharing relationships. As a result, Eclipse <b>does not allow</b>
+ to   any    sharing relationships. As a result, Eclipse <b>does not allow</b>
  plug-ins    to be installed using native installers into the shared installation
  tree.    Instead, native installers must establish their own installation
- root directory.    The subdirectory structure is the same as defined for base
+  root directory.    The subdirectory structure is the same as defined for
- Eclipse. The  private  root directory is logically linked into the shared
+ base Eclipse. The  private  root directory is logically linked into the shared
    Eclipse installation   via  a link file installed by the native installer.
    The file path for the   link  file is <tt>&lt;configRoot&gt;/links/</tt>.
    The <tt>&lt;configRoot&gt;   </tt>  location is computed by Eclipse relative
    to the launch <a href="#Multiple%20Launch%20Points"> configuration file</a>
-   . By default,    this is the <tt>install/</tt> directory in the shared Eclipse
+    . By default,    this is the <tt>install/</tt> directory in the shared
-   installation    tree. </p>
+ Eclipse   installation    tree. </p>
  <p>The name of the link file is not specified by Eclipse. The name is determined
        by the native installer. To minimize the potential for naming collisions,
        it is recommended that the file name contain the identifier and version
-     of the feature being installed by the native installer. For example, <tt>&lt;featureId&gt;_&lt;featureVersion&gt;.properties</tt>
+      of the feature being installed by the native installer. For example,
-      . The file content is in the form of a Java properties file, with the
+ <tt>&lt;featureId&gt;_&lt;featureVersion&gt;.properties</tt>      . The file
-  following    properties defined: </p>
+ content is in the form of a Java properties file, with the  following
+ properties defined: </p>
  <p><tt>path=[r|rw] install-path[,[r|rw] install-path]*</tt> </p>
  <p>The property <tt>path</tt> is a comma-separated list of optionally annotated
-       install paths. The property value <tt>install-path</tt> is a full file
+        install paths. The property value <tt>install-path</tt> is a full
-    path  to the installation directory root, specified in local OS format.
+ file     path  to the installation directory root, specified in local OS
-  The  optional  annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse
+ format.   The  optional  annotation <tt>r</tt> or <tt>rw</tt> indicates whether
-   update support  should allow the specified location to be used for updates.
+ Eclipse    update support  should allow the specified location to be used
-   Default is to  allow updates&nbsp; (w). </p>
+ for updates.    Default is to  allow updates&nbsp; (w). </p>
  <p>Eclipse does not manage the linked directories in any way. It simply detects
        their existence by the presence of the link files, and includes the
-Line 1455
+Line 1477
           <br>
    <br>
   <br>
+  <br>
  </body>
  </html>

 Legend:



Removed from v.1.17
 


changed lines


 
Added in v.1.18
 Legend:



Removed from v.1.17
 


changed lines


 
Added in v.1.18
-Removed from v.1.17
+Added in v.1.18

help@eclipse.org	ViewVC Help
Powered by ViewVC 1.0.3