platform-update-home/doc/eclipse_update_packaging.html

Parent Directory | Revision Log | Patch

-revision 1.13, Mon Jan 13 19:01:27 2003 UTC
+revision 1.14, Wed Jan 15 15:30:07 2003 UTC
 Line 9
    <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
    <title>Eclipse Platform: Installation and Update</title>
  </head>
    <body>
  <h1> Eclipse Platform<br>
        Update Packaging Conventions</h1>
-       <font size="-1">Revision Date: 01/02/2003 9:33AM - Version: 2.0.16</font><br>
+           <font size="-1">Revision Date: 01/15/2003 9:33AM - Version: 2.0.17</font><br>
       <a href="../../../../../hglegal.htm"><img src="ngibmcpy.gif"
   border="0" height="12" width="195">
       </a>
  <p><b>Change History:</b> </p>
  <ul>
+            <li><small>2.0.17</small></li>
+   <ul>
+     <li><small>added $os$,$ws$,$arch$ and $nl$ for copyright, description
+ and license URL tag in feature.<br>
+       </small></li>
+   </ul>
         <li><small>2.0.16</small>     <small><br>
        </small>
      <ul>
-Line 44
+Line 51
      </ul>
        </li>
-       <li><font size="-1">2.0.13</font>             <small><br>
+           <li><small>2.0.13<br>
-        </small>
+            </small> </li>
      <ul>
           <li><small>added &lt;includes name,optional,match,search_location</small>
    &gt;</li>
           <li><small>added &lt;import feature,patch&gt;</small></li>
      </ul>
-      </li>
+                          <li><small>2.0.12<br>
+       </small></li>
- </ul>
- <ul>
-        <li><font size="-1">2.0.12</font></li>
    <ul>
        <li> <font size="-1">added reference to the <a
-Line 85
+Line 89
  up  searches</font></li>
         <li> <font size="-1">removed obsolete text</font></li>
         <li> <font size="-1">web-triggered update not in 2.0</font></li>
-        <li> <font size="-1">no assist in 2.0 for license/ "key file" handling
+            <li> <font size="-1">no assist in 2.0 for license/ "key file"
-   (individual application/ plugin responsibility)</font></li>
+ handling     (individual application/ plugin responsibility)</font></li>
    </ul>
         <li> <font size="-1">2.0.8</font></li>
-Line 119
+Line 123
        <li> <font size="-1">general text cleanup</font></li>
         <li> <font size="-1">&lt;feature&gt;&lt;group&gt; support 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">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 support</font></li>
+            <li> <font size="-1">corrected errors in native installer link
+ support</font></li>
         <li> <font size="-1">defined callback query strings for browser-triggered
    processing</font></li>
-Line 132
+Line 138
  <h3> <font size="+2">Table of Contents</font></h3>
        <a href="#Introduction">Introduction</a>  <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Changes_from_R1.0">Changes
+          &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-    from 1.0</a>  <br>
+  href="#Changes_from_R1.0">Changes     from 1.0</a>  <br>
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Concepts">Concepts</a>
    <br>
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Framework">Framework</a>
-Line 168
+Line 174
       <a href="#Update_Server">Update Server</a>  <br>
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Site_Map">Site Map</a>
    <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Default_Site_Layout">Default
+          &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-    Site Layout</a>  <br>
+  href="#Default_Site_Layout">Default    Site Layout</a>  <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Controlling_Access">Controlling
+          &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-    Access</a>  <br>
+  href="#Controlling_Access">Controlling     Access</a>  <br>
       <a href="#Eclipse_Install">Eclipse Install</a>  <br>
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
   href="#Default_Install_Layout">Default   Install Layout</a>  <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Unmanaged_Plugins">"Unmanaged"
+          &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-    Plug-Ins</a>  <br>
+  href="#Unmanaged_Plugins">"Unmanaged"     Plug-Ins</a>  <br>
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
   href="#Using_Native_Platform_Installers"> Using Native Platform Installers</a>
  <h2> <a name="Introduction"></a> Introduction</h2>
-       This document outlines the support for managing the delivery of function
+           This document outlines the support for managing the delivery of
-    within the Eclipse platform. Also refer to the "<a
+ 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
  use   of the Eclipse update manager function.
-Line 193
+Line 199
  <ul>
        <li> <b>extendable framework</b></li>
         <br>
-      In R2.0 Eclipse defines an extendable framework for installation and
+          In R2.0 Eclipse defines an extendable framework for installation
- update,   allowing the support for alternate packaging and site management
+ and   update,   allowing the support for alternate packaging and site management
  schemes.   R2.0 supplies a default concrete implementation of this framework.
    <li>     <b>  feature support</b></li>
         <br>
-      In R2.0 the concept of a <i>component</i> and <i>configuration</i> is
+          In R2.0 the concept of a <i>component</i> and <i>configuration</i>
-  merged  into <i>feature</i>. Features define the packaging structure for
+  is  merged  into <i>feature</i>. Features define the packaging structure
- a group of related plug-ins, plug-in fragments, and optionally non-plug-in
+ 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
  nest. They are simply an inclusive "manifest" of the plug-ins, fragments
-Line 208
+Line 214
  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>
         <br>
-      R1.0 components were packaged as a single Java .jar containing the component
+          R1.0 components were packaged as a single Java .jar containing the
-   manifest as well as the actual plug-in files. The problem with this approach
+  component    manifest as well as the actual plug-in files. The problem with
-   is lack of granularity at download time. In R2.0, the feature archive consists
+  this approach    is lack of granularity at download time. In R2.0, the feature
-   of multiple separate .jars - one .jar per plug-in and fragment, plus one
+  archive consists    of multiple separate .jars - one .jar per plug-in and
-  .jar for the actual feature information. The Installation and Update support
+  fragment, plus one   .jar for the actual feature information. The Installation
-  selectively downloads only those jars required for the installation. <li>
+  and Update support   selectively downloads only those jars required for the
-   <b>site map</b></li>
+  installation. <li>    <b>site map</b></li>
-        <br>
+            <br>
-      Default Eclipse update server must contain a <i>site map</i> file (site.xml).
+          Default Eclipse update server must contain a <i>site map</i> file
-    This is an evolution of the R1.0 install.index support. The rationale
+  (site.xml).     This is an evolution of the R1.0 install.index support.
- for    using a structured site defined by the map rather than a "free form"
+ The  rationale for    using a structured site defined by the map rather than
- web   site, is the ability to present a consistent installation experience
+ a  "free form" web   site, is the ability to present a consistent installation
- for  the user. Also, this provides the necessary structure for discovery
+  experience for  the user. Also, this provides the necessary structure for
- of available   updates. Additional support for "free form" browsing may be
+  discovery of available   updates. Additional support for "free form" browsing
- considered in   future work.    <li> <b>using native install/ uninstall</b></li>
+  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 primary mechanism for installing and updating Eclipse features
-  the  built-in installation and update support. Some products may instead
+  is  the  built-in installation and update support. Some products may instead
  choose  to use native installer technology (eg. MSI, RPM, etc) to deliver
  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
  needed by other features. As a result, features installed using native installers
-  must be written into private product-specific installation location and not
+    must be written into private product-specific installation location and
-  the shared Eclipse installation location. The shared Eclipse is made aware
+  not  the shared Eclipse installation location. The shared Eclipse is made
-  of the produce-specific location via an installed "link file". <li>
+  aware  of the produce-specific location via an installed "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. To accommodate
-  this,  R2.0 Eclipse supports custom install handlers packaged as part of
+    this,  R2.0 Eclipse supports custom install handlers packaged as part
- the feature  and executed during the feature installation. <li> <b>path naming
+ of   the feature  and executed during the feature installation. <li> <b>path
-  conventions</b></li>
+ 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 requirements
-   no longer mandate that path names of packaged files precisely reflect the
+     no longer mandate that path names of packaged files precisely reflect
-   contained identifiers and versions. The properly identified install subdirectories
+ the    contained identifiers and versions. The properly identified install
-   are created by the Eclipse support during the installation and update process
+ subdirectories    are created by the Eclipse support during the installation
-    based on the archive content (rather than explicit jar path structure
+ and update process     based on the archive content (rather than explicit
- set    up at packaging time)
+ jar path structure set    up at packaging time)
  </ul>
  <h3> <a name="Concepts"></a> Concepts</h3>
        <b>Plug-in</b> <br>
-      Eclipse developers build plug-ins. Plug-ins are the base units of execution
+          Eclipse developers build plug-ins. Plug-ins are the base units of
-    recognized by the Eclipse runtime environment. In general, plug-ins are
+  execution     recognized by the Eclipse runtime environment. In general,
-  not exposed to users that select function during installation or update.
+ plug-ins are   not exposed to users that select function during installation
- The reason is that plug-in boundaries are established by developers for development
+ or update.  The reason is that plug-in boundaries are established by developers
-   reasons (like function reuse) and present the wrong level of granularity
+ for development    reasons (like function reuse) and present the wrong level
-  in terms of what the user sees as the unit of function.
+ 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.
+      their internal file structure will reflect what is convenient to the
-    This will generally depend on the particular development tool being used.
+ developer.     This will generally depend on the particular development tool
-    Typically, however, the developer will likely setup the plug-in to execute
+ being used.     Typically, however, the developer will likely setup the plug-in
-    from a directory tree containing exposed .class files, rather than executing
+ to execute     from a directory tree containing exposed .class files, rather
-    from a .jar (requires an extra step to create the .jar and we all know
+ than executing     from a .jar (requires an extra step to create the .jar
- developers  hate extra steps). Also, at this stage the developer does not
+ and we all know  developers  hate extra steps). Also, at this stage the developer
- pay particular  attention to plug-in versioning information, because the
+ does not  pay particular  attention to plug-in versioning information, because
- plug-in is continually  changing. </p>
+ 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
  creation    of the runtime .jar(s) and removing any development-time files
  (source,  exposed .class files, etc). It also means updating the plugin.xml
- manifest  with the formal plug-in version and reflecting the version in the
+  manifest  with the formal plug-in version and reflecting the version in
- plug-in  directory name (see "Concurrent Plug-In Version Support" for details).
+ the  plug-in  directory name (see "Concurrent Plug-In Version Support" for
- </p>
+ details).  </p>
  <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 limited
+   of  certain  aspects of the base plug-in. This includes (but may not be
-  to) translated  resources for the plug-in, OS-specific or windowing-system-specific
+ limited   to) translated  resources for the plug-in, OS-specific or windowing-system-specific
   code.  At runtime, fragments are logically merged into the base plug-in.
- From a packaging point of view, the install and update support does not really
+   From a packaging point of view, the install and update support does not
-  differentiate  between plug-ins and their related fragments. </p>
+ 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
+          A feature is an installation packaging mechanism used to define
-   of versioned plug-ins and/or plug-in fragments plus non-plug-in files that
+ a  group    of versioned plug-ins and/or plug-in fragments plus non-plug-in
-   is used to deliver some user function. A feature can also include other
+ files that    is used to deliver some user function. A feature can also include
- features.  Features are exposed to users as part of the packaging and installation
+  other  features.  Features are exposed to users as part of the packaging
-  process,  because they represent a unit of function selection. Features also
+ and installation   process,  because they represent a unit of function selection.
-  represent  a unit of installation. Features carry a version identifier.</p>
+  Features also  represent  a unit of installation. Features 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
+     plug-in fragments and optional non-plug-in files. The feature archives
-   placed on an update server for download and installation by the Eclipse
+  are   placed on an update server for download and installation by the Eclipse
  update  manager, or they can be used as the input into a formal packaging
  process  using one of the "traditional" installer technologies. The format
  of the feature archive is described later. </p>
-Line 311
+Line 319
  can   be used to support alternate packaging schemes. New concrete feature
  types   are  registere via the "org.eclipse.update.featureTypes" extension
  point.</li>
-        <li> concrete implementations of site (ISite interface) that can be
+            <li> concrete implementations of site (ISite interface) that can
-  used  to support alternate site layout, or site behavior. New concrete site
+  be  used  to support alternate site layout, or site behavior. New concrete
-  types   are registered via the "org.eclipse.update.siteTypes" extension
+  site  types   are registered via the "org.eclipse.update.siteTypes" extension
  point.</li>
-        <li> each feature can specify a custom install handler as part of
+            <li> each feature can specify a custom install handler as part
- its   feature  manifest. Install handlers (IInstallHandler interface) are
+ of  its   feature  manifest. Install handlers (IInstallHandler interface)
- dynamically   invoked as part of the installation process to handle non-plugin
+ are  dynamically   invoked as part of the installation process to handle non-plugin
  data, plus   perform other custom processing allowed by the framework.</li>
  </ul>
-Line 341
+Line 349
  <h2> <a name="Packaging_Conventions"></a> Packaging Conventions</h2>
        Default feature packages consist of several related files:
  <ul>
-       <li> exactly one jar containing the feature manifest and related files.
+           <li> exactly one jar containing the feature manifest and related
-   This one is refered to as the "<b>feature archive</b>"</li>
+  files.    This one is refered to as the "<b>feature archive</b>"</li>
-        <li> zero or more jars containing the feature plug-ins. These are
+            <li> zero or more jars containing the feature plug-ins. These
- refered   to as the "<b>plug-in archives</b>"</li>
+ are   refered   to as the "<b>plug-in archives</b>"</li>
-        <li> zero or more non-plug-in files associated with the feature. They
+            <li> zero or more non-plug-in files associated with the feature.
-   are used by feature custom install handlers and contain data not interpreted
+  They   are used by feature custom install handlers and contain data not interpreted
    by Eclipse</li>
  </ul>
  <h3> <a name="Feature_Archive"></a> Feature Archive</h3>
-       The feature packaging information is placed into a separate Java .jar.
+           The feature packaging information is placed into a separate Java
-   Standard Java jar facilities are used for constructing feature archives.
+  .jar.    Standard Java jar facilities are used for constructing feature
-  Feature archives reference separately packaged plug-in archives (see next
+ archives.    Feature archives reference separately packaged plug-in archives
-  section) and non-plug-in files.
+ (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
-Line 385
+Line 394
     <br>
       <tt>other feature files and subdirectories (TBD)</tt> <br>
       <tt>META-INF/</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt> </p>
+          <tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
+ </p>
  <p>The feature install.xml format is defined by the following dtd: </p>
-Line 396
+Line 406
       <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>
-      <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #REQUIRED</tt> <br>
+  CDATA    #REQUIRED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     CDATA #IMPLIED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; provider-name CDATA #IMPLIED</tt> <br>
-Line 414
+Line 424
       <tt>&nbsp;&nbsp;&nbsp; colocation-affinity</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     CDATA #IMPLIED</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; primary&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true
+          <tt>&nbsp;&nbsp;&nbsp; primary&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   | false) "false"</tt> <br>
+  (true    | false) "false"</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; application&nbsp;&nbsp; CDATA #IMPLIED</tt> <br>
+          <tt>&nbsp;&nbsp;&nbsp; application&nbsp;&nbsp; CDATA #IMPLIED</tt>
+  <br>
       <tt>&gt;</tt> </p>
  <p><tt>&lt;!ELEMENT install-handler EMPTY&gt;</tt> <br>
       <tt>&lt;!ATTLIST install-handler</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; library&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; library&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #IMPLIED</tt> <br>
+  CDATA    #IMPLIED</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #IMPLIED</tt> <br>
+  CDATA    #IMPLIED</tt> <br>
       <tt>&gt;</tt> </p>
  <p><tt>&lt;!ELEMENT description (#PCDATA)&gt;</tt> <br>
-Line 467
+Line 478
       <tt>&lt;!ATTLIST includes</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     &nbsp;&nbsp;&nbsp; CDATA #REQUIRED</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+          <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   CDATA #REQUIRED</tt>&nbsp;<br>
+  &nbsp;&nbsp;&nbsp;    CDATA #REQUIRED</tt>&nbsp;<br>
       <tt>&nbsp;&nbsp;&nbsp; name &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;
    &nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; optional &nbsp;&nbsp;&nbsp;&nbsp; </tt><tt>&nbsp;&nbsp;&nbsp;
-Line 488
+Line 499
    CDATA #IMPLIED</tt><br>
       <tt>&nbsp;&nbsp;&nbsp; feature &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
  #IMPLIED</tt><br>
-      <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #IMPLIED</tt> <br>
+  CDATA    #IMPLIED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; match&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
   &nbsp;(perfect  | equivalent | compatible | greaterOrEqual) "compatible"</tt>&nbsp;<br>
       <tt>&nbsp;&nbsp;&nbsp; patch &nbsp;&nbsp;&nbsp;&nbsp; </tt><tt>&nbsp;&nbsp;
-Line 501
+Line 512
       <tt>&lt;!ATTLIST plugin</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     CDATA #REQUIRED</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #REQUIRED</tt> <br>
+  CDATA    #REQUIRED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; fragment&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true
  |  false)  "false"</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Line 541
+Line 552
    <ul>
        <li> id - required feature identifier (eg. com.xyz.myfeature)</li>
         <li> version - required component version (eg. 1.0.3)</li>
-        <li> label - optional displayable label (name). Intended to be translated.</li>
+            <li> label - optional displayable label (name). Intended to be
+ translated.</li>
         <li> provider-name - optional display label identifying the organization
    providing this component. Intended to be translated.</li>
-        <li> image - optional image to use when displaying information about
+            <li> image - optional image to use when displaying information
-  the  feature.&nbsp; Specified relative to the feature.xml.</li>
+ about    the  feature.&nbsp; Specified relative to the feature.xml.</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 feature should only be installed on one of the specified
-Line 554
+Line 566
  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>
+     list of architecture designators defined by Eclipse (see Javadoc for
-   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
+      <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature
-   be installed on one of the specified systems. If this attribute is not specified,
+ should only    be installed on one of the specified systems. If this attribute
-   the feature can be installed on all systems (portable implementation). This
+ is not specified,   the feature can be installed on all systems (portable
-   information is used as a hint by the installation and update support (user
+ implementation).  This   information is used as a hint by the installation
-   can force installation of feature regardless of this setting).</li>
+ 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
-Line 567
+Line 580
     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> nl - optional locale specification. A comma-separated list of
+            <li> nl - optional locale specification. A comma-separated list
- locale   designators defined by Java. Indicates this feature should only be
+  of  locale   designators defined by Java. Indicates this feature should
- installed   on a system running with a compatible locale (using Java locale-matching
+ only  be installed   on a system running with a compatible locale (using
-  rules). If this attribute is not specified, the feature can be installed
+ Java locale-matching    rules). If this attribute is not specified, the feature
- on all systems (language-neutral implementation). This information is used
+ can be installed   on all systems (language-neutral implementation). This
- as a hint by the installation and update support (user can force installation
+ information is used   as a hint by the installation and update support (user
-  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
+            <li> colocation-affinity - optional reference to another feature
-    used to select the default installation location for this feature. When
+  identifier    used to select the default installation location for this feature.
-  this feature is being installed as a new feature (no other versions of it
+  When  this feature is being installed as a new feature (no other versions
-  are installed), an attempt is made to install this feature in the same installation
+  of it  are installed), an attempt is made to install this feature in the
-   location as the referenced feature.</li>
+ same installation    location as the referenced feature.</li>
         <li> primary - optional indication specifying whether this feature
  can   be used as a <a href="#Dominant_Feature">primary feature</a> . Default
  if        <i>false</i> (not a primary feature).</li>
-Line 595
+Line 608
        <li> library - optional .jar library containing the install handler
  classes.   If specified, the referenced .jar must be contained in the feature
  archive.   It is specified as a path within the feature archive, relative
- to the feature.xml   entry. If not specified, the feature archive itself is
+   to the feature.xml   entry. If not specified, the feature archive itself
- used to load the install handler classes. This attribute is only interpreted
+  is used to load the install handler classes. This attribute is only interpreted
  if <i>class</i> attribute is also specified</li>
-        <li> handler - optional identifier of the install handler. The value
+            <li> handler - optional identifier of the install handler. The
-  is  interpreted depending on the value of the <i>library</i> attribute. If
+ value    is  interpreted depending on the value of the <i>library</i> attribute.
-        <i>  library</i> is specified,&nbsp; the value is interpreted as a
+  If        <i>  library</i> is specified,&nbsp; the value is interpreted as
- fully qualified  name of a class contained in the specified <i>library</i>.
+  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
+   If       <i>library</i>   is not specified, the value is is interpreted
- an extension identifier  of an extension registered in the <i>org.eclipse.update.installHandlers</i>
+ as  an extension identifier  of an extension registered in the <i>org.eclipse.update.installHandlers</i>
     extension point. In 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
-Line 611
+Line 624
  required by the update plugin.</li>
    </ul>
-        <li> &lt;description&gt; - brief component description as simple text.
+            <li> &lt;description&gt; - brief component description as simple
-   Intended to be translated.</li>
+  text.    Intended to be translated.</li>
    <ul>
-       <li> url - optional URL for the full description as HTML. The URL can
+           <li> url - optional URL for the full description as HTML. The URL
-  be  specified as absolute of relative. If relative, it is assumed to be relative
+  can   be  specified as absolute of relative. If relative, it is assumed to
-   to (and packaged in) the feature archive. Note, that for NL handling the
+  be relative   to (and packaged in) the feature archive. Note, that for NL
-  URL value should be separated to allow alternate URLs to be specified for
+  handling the  URL value should be separated to allow alternate URLs to be
-  each national language.</li>
+  specified for  each national language. &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>
    </ul>
         <li> &lt;copyright&gt; - feature copyright as simple text. Intended
   to  be translated.</li>
    <ul>
-       <li> url - optional URL for the full description as HTML. The URL can
+           <li> url - optional URL for the full description as HTML. The URL
-  be  specified as absolute of relative. If relative, it is assumed to be relative
+  can   be  specified as absolute of relative. If relative, it is assumed to
-   to (and packaged in) the feature archive. Note, that for NL handling the
+  be relative   to (and packaged in) the feature archive. Note, that for NL
-  URL value should be separated to allow alternate URLs to be specified for
+  handling the  URL value should be separated to allow alternate URLs to be
-  each national language.</li>
+  specified for  each national language. URL support keywords $os$,$ws$,$arch$
+ and $nl$ that will be replaced by the appropriate operating system, windowing
-   </ul>
+ system, operating architecture or national language value.</li>
-        <li> &lt;license&gt; - feature "click-through" license as simple text.
-   Intended to be translated. It is displayed in a standard dialog with [Accept]
+   </ul>
-   [Reject] actions during the download/ installation process. Note, that click-through
+            <li> &lt;license&gt; - feature "click-through" license as simple
-   license must be specified for any feature that will be selected for installation
+  text.    Intended to be translated. It is displayed in a standard dialog
-   or update using the Eclipse update manager. When using nested features,
+ with [Accept]    [Reject] actions during the download/ installation process.
- only the nesting parent (ie. the feature selected for installation or update)
+ Note, that click-through   license must be specified for any feature that
- must have click-through license text defined. The license text is required
+ will be selected for installation   or update using the Eclipse update manager.
- even if the optional <i>url</i> attribute is specified.</li>
+  When using nested features, only the nesting parent (ie. the feature selected
+  for installation or update) must have click-through license text defined.
-   <ul>
+  The license text is required even if the optional <i>url</i> attribute is
-       <li> url - optional URL for the full description as HTML. The URL can
+  specified.</li>
-  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
+   <ul>
-  URL value should be separated to allow alternate URLs to be specified for
+           <li> url - optional URL for the full description as HTML. The URL
-  each national language. Note, that the "content" of this URL is <b>not</b>
+  can   be  specified as absolute of relative. If relative, it is assumed to
-   what is presented as the click-through license during installation processing.
+  be relative   to (and packaged in) the feature archive. Note, that for NL
-   The click-through license is the actual value of the <i>&lt;license&gt;</i>
+  handling the  URL value should be separated to allow alternate URLs to be
-    element (eg. <tt>&lt;license&gt;click through text&lt;/license&gt;</tt>)</li>
+  specified for  each national language. Note, that the "content" of this URL
+  is <b>not</b>    what is presented as the click-through license during installation
+  processing.    The click-through license is the actual value 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>
    </ul>
         <li> &lt;url&gt; - optional URL specifying site(s) contain feature
-Line 676
+Line 697
      </ul>
    </ul>
-        <li> &lt;includes&gt; - optional reference to a nested feature that
+            <li> &lt;includes&gt; - optional reference to a nested feature
-  is  considered to be part of this feature. Nested features must be located
+ that   is  considered to be part of this feature. Nested features must be
-  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>
         <li> version - required nested feature version</li>
-          <li> name- optional displayable label (name). Intended to be translated.</li>
+              <li> name- optional displayable label (name). Intended to be
+ translated.</li>
           <li>optional - optional specification indicating if this 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 that matches
+     the feature reference. A <samp>perfect</samp> match (the default that
-   the 2.0.1 behavior) requires that the feature has exactly the version specified
+ matches    the 2.0.1 behavior) requires that the feature has exactly the
-   by the version attribute. Other choices progressively relax the rule (<samp>
+ version specified    by the version attribute. Other choices progressively
-   equivalent</samp> allows only service part of the version to be more recent,
+ relax the rule (<samp>    equivalent</samp> allows only service part of the
-         <samp>compatible</samp> also allows minor part to be included in the
+ version to be more recent,          <samp>compatible</samp> also allows minor
-   consideration, while <samp>greaterOrEqual</samp> simply allows any version
+ part to be included in the   consideration, while <samp>greaterOrEqual</samp>
-   that is more recent or identical to the one specified).</li>
+  simply allows any version   that is more recent or identical to the one specified).</li>
-          <li>search_location&nbsp; - optional. Indicates whether the "New
+              <li>search_location&nbsp; - optional. Indicates whether the
- Updates"   action should search the update location determined by the nesting
+ "New   Updates"   action should search the update location determined by
- root feature  (<tt>root</tt>, is the default), or the location defined by
+ the nesting   root feature  (<tt>root</tt>, is the default), or the location
- the nested feature  (<tt>self</tt>), or search both (<tt>both</tt>) in that
+ defined by   the nested feature  (<tt>self</tt>), or search both (<tt>both</tt>)
- order (root first,  self if nothing is found).</li>
+ in that   order (root first,  self if nothing is found).</li>
    </ul>
-        <li> &lt;requires&gt; - optional feature dependency information. Is
+            <li> &lt;requires&gt; - optional feature dependency information.
-  expressed  in terms of plug-in dependencies. If specified, is enforced by
+  Is  expressed  in terms of plug-in dependencies. If specified, is enforced
-  the installation   and update support at the time of installation</li>
+  by  the installation   and update support at the time of installation</li>
    <ul>
        <li> &lt;import&gt; - dependency entry. Specification and processing
-Line 712
+Line 734
      <ul>
        <li> plugin - identifier of dependent plug-in.</li>
-            <li> feature - identifier of dependent feature. If plugin and
+                <li> feature - identifier of dependent feature. If plugin
- feature   are specified, plugin takes precedence upon feature. Feature or
+ and   feature   are specified, plugin takes precedence upon feature. Feature
- plugin must   be specified.</li>
+ or   plugin must   be specified.</li>
         <li> version - optional plug-in/feature version specification</li>
             <li>patch - optional specification indicating if this feature
- is  a  patch of the dependant feature. Default is "false". If patch is true,
+   is  a  patch of the dependant feature. Default is "false". If patch is
- version  must be specified. If patch is true, only feature must be specified.
+ true,   version  must be specified. If patch is true, only feature must be
- If patch  is true, and match is specified, it must be 'perfect'.<br>
+ 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
+            <li> match - optional matching rule. Valid values and processing
-  as  follows:</li>
+  are   as  follows:</li>
        <ul>
-       <li> if version attribute is not specified, the match attribute (if
+           <li> if version attribute is not specified, the match attribute
- specified)   is ignored.</li>
+ (if   specified)   is ignored.</li>
               <li>if version is specified, match defaults to compatible.<br>
               </li>
-              <li>if patch is true, and match is not specified, match defaults
+                  <li>if patch is true, and match is not specified, match
-   to perfect.<br>
+ defaults     to perfect.<br>
               </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 be
+            <li> <b><i>equivalent</i></b> - dependent plug-in version must
- at  least  at the version specified, or at a higher service level (major
+ be  at  least  at the version specified, or at a higher service level (major
  and minor version  levels must equal the specified version).</li>
-        <li> <b><i>compatible</i></b> - dependent plug-in version must be
+            <li> <b><i>compatible</i></b> - dependent plug-in version must
- at  least  at the version specified, or at a higher service level or minor
+ be  at  least  at the version specified, or at a higher service level or minor
  level  (major  version level must equal the specified version).</li>
-        <li> <b><i>greaterOrEqual</i></b> - dependent plug-in version must
+            <li> <b><i>greaterOrEqual</i></b> - dependent plug-in version
- be  at least at the version specified, or at a higher service, minor or major
+ must   be  at least at the version specified, or at a higher service, minor
-   level.</li>
+ or major   level.</li>
        </ul>
-Line 754
+Line 777
    <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 is
+            <li> fragment - optional specification indicating if this entry
- a  plug-in  fragment. Default is "false"</li>
+  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 a
+     on all systems (portable implementation). This information is used as
- hint  by the installation and update support (user can force installation
+ 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>
+     list of architecture designators defined by Eclipse (see Javadoc for
-   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
+      <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature
-   be installed on one of the specified systems. If this attribute is not specified,
+ should only    be installed on one of the specified systems. If this attribute
-   the feature can be installed on all systems (portable implementation). This
+ is not specified,   the feature can be installed on all systems (portable
-   information is used as a hint by the installation and update support (user
+ implementation).  This   information is used as a hint by the installation
-   can force installation of feature regardless of this setting).</li>
+ 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 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 a
+     on all systems (portable implementation). This information is used as
- 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 only be
- installed   on a system running with a compatible locale (using Java locale-matching
-  rules). If this attribute is not specified, the entry can be installed on
-  all systems (language-neutral implementation). This information is used 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 only
+  be  installed   on a system running with a compatible locale (using Java
+ locale-matching   rules). If this attribute is not specified, the entry can
+ be installed on   all systems (language-neutral implementation). This 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 plug-in archive.
   If not specified,  the download size is not known (<b>Implementation Note:</b>
-Line 794
+Line 818
   the implementation   needs to distinguish between "not known" and 0 size)</li>
    </ul>
-        <li> &lt;data&gt; - identifies non-plugin and non-feature data that
+            <li> &lt;data&gt; - identifies non-plugin and non-feature data
- is part of the feature. Generally, data are post-install processed using
+ 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 805
+Line 829
   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 a
+     on all systems (portable implementation). This information is used as
- hint  by the installation and update support (user can force installation
+ 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>
+     list of architecture designators defined by Eclipse (see Javadoc for
-   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
+      <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature
-   be installed on one of the specified systems. If this attribute is not specified,
+ should only    be installed on one of the specified systems. If this attribute
-   the feature can be installed on all systems (portable implementation). This
+ is not specified,   the feature can be installed on all systems (portable
-   information is used as a hint by the installation and update support (user
+ implementation).  This   information is used as a hint by the installation
-   can force installation of feature regardless of this setting).</li>
+ 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 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 a
+     on all systems (portable implementation). This information is used as
- 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 only be
- installed   on a system running with a compatible locale (using Java locale-matching
-  rules). If this attribute is not specified, the entry can be installed on
-  all systems (language-neutral implementation). This information is used 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 only
+  be  installed   on a system running with a compatible locale (using Java
+ locale-matching   rules). If this attribute is not specified, the entry can
+ be installed on   all systems (language-neutral implementation). This 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 data archive. If
+    indicating  the download size in KBytes of the referenced data archive.
-  not specified,  the download size is not known (<b>Implementation Note:</b>
+  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.
-Line 843
+Line 868
  </ul>
        <a name="Feature_Archive_Mapping_Id_To_Path"></a> When interacting
  with   the update site, the feature implementation maps the <tt>&lt;plugin&gt;</tt>
-   and <tt>&lt;data&gt;</tt> elements into path identifiers used by the site
+     and <tt>&lt;data&gt;</tt> elements into path identifiers used by the
-   to determine the actual files to download and install. The default feature
+ site     to determine the actual files to download and install. The default
-   implementation supplied by Eclipse constructs the path identifiers as follows:
+ feature     implementation supplied by Eclipse constructs the path identifiers
+ as follows:
  <ul>
-       <li> <tt>&lt;plugin&gt;</tt> element results in a path entry in the
+           <li> <tt>&lt;plugin&gt;</tt> element results in a path entry in
- form   "<tt>plugins/&lt;pluginId&gt;_&lt;pluginVersion&gt;.jar</tt>" (for
+ the   form   "<tt>plugins/&lt;pluginId&gt;_&lt;pluginVersion&gt;.jar</tt>"
- example,   "<tt>plugins/org.eclipse.core.boot_1.0.3.jar</tt>")</li>
+ (for   example,   "<tt>plugins/org.eclipse.core.boot_1.0.3.jar</tt>")</li>
-        <li> <tt>&lt;data&gt;</tt> element results in a path entry in the
+            <li> <tt>&lt;data&gt;</tt> element results in a path entry in
- form   "<tt>features/&lt;featureId&gt;_&lt;featureVersion&gt;/&lt;dataId&gt;</tt>
+ the   form   "<tt>features/&lt;featureId&gt;_&lt;featureVersion&gt;/&lt;dataId&gt;</tt>
    " (for example, "f<tt>eatures/com.xyz.tools_2.3.1/examples.zip</tt>")</li>
  </ul>
-       Note, that in general the feature.xml&nbsp; manifest documents should
+           Note, that in general the feature.xml&nbsp; manifest documents
-  specify  UTF-8 encoding. For example
+ should    specify  UTF-8 encoding. For example
  <p><tt>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</tt> </p>
  <p>Translatable text contained in the feature.xml can be separated into feature&lt;_locale&gt;.properties
-   files using Java property bundle conventions. Note that the translated strings
+     files using Java property bundle conventions. Note that the translated
-   are used at installation time (ie. do not employ the plug-in fragment runtime
+  strings   are used at installation time (ie. do not employ the plug-in fragment
-   mechanism). </p>
+  runtime   mechanism). </p>
  <h3> <a name="Plug-In_Archive"></a> Plug-In Archive</h3>
        Plug-ins and plug-in fragments are individually packaged as separate
-Line 875
+Line 900
  <p>Where <tt>&lt;id&gt;</tt> is the plug-in or fragment identifier and <tt>
    &lt;version&gt;</tt> is the full version identifier contained in the respective
-   plugin.xml or fragment.xml. Note that this is a recommended convention that
+     plugin.xml or fragment.xml. Note that this is a recommended convention
-   minimizes chance of collisions, but is not required by the Eclipse architecture.
+  that   minimizes chance of collisions, but is not required by the Eclipse
-   For example, the following are valid plug-in archive names </p>
+  architecture.   For example, the following are valid plug-in archive names
+  </p>
  <p><tt>org.eclipse.platform_1.0.3.jar</tt> <br>
       <tt>org.eclipse.ui.nl_2.0.jar</tt> <br>
-Line 890
+Line 916
  <p><tt>plugin.xml *OR* fragment.xml</tt> <br>
       <tt>other plug-in or feature files and subdirectories</tt> <br>
       <tt>META-INF/</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt> </p>
+          <tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
+ </p>
  <h3> <a name="Packaging_NL"></a> Packaging NL</h3>
        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
+     with the base plug-in, or as a plug-in fragment. At runtime, Eclipse
-   the translations for the required locale. The use of fragments allows translations
+ locates     the translations for the required locale. The use of fragments
-    to be added to the runtime without the need to repackage the base plug-ins.
+ allows translations     to be added to the runtime without the need 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, and
+  Java    translation conventions are used for the packaging information,
- all  necessary translations must be available at the time the feature is
+ and  all  necessary translations must be available at the time the feature
- packaged.  </p>
+ is packaged.  </p>
  <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 allows for the
+      the information contained within the feature manifest. It allows for
-   update client to select the correctly localized strings from the update
+ the    update client to select the correctly localized strings from the update
  server.  This section specifically does not describe localization of individual
  plug-ins.
  <p>Several of the attributes within the feature manifest are strings intended
-Line 935
+Line 962
  <p><tt>ResourceBundle b;</tt> <br>
       <tt>ClassLoader l;</tt> <br>
-      <tt>l = new URLClassLoader(new URL[] {&lt;targetDirectoryURL&gt;}, null);</tt>
+          <tt>l = new URLClassLoader(new URL[] {&lt;targetDirectoryURL&gt;},
-    <br>
+  null);</tt>     <br>
       <tt>b = ResourceBundle.getBundle("feature",Locale.getDefault(),l);</tt>
    </p>
-Line 967
+Line 994
  <h3> <a name="Custom_Install_Handling"></a> Custom Install Handling</h3>
        Custom install handlers are written as a Java class and are 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
+     must implement the <tt>IInstallHandler</tt> interface (in most cases
-   extend the <tt>BaseInstallHandler</tt> abstract helper class which implements
+ will     extend the <tt>BaseInstallHandler</tt> abstract helper class which
-   <tt>IInstallHandler</tt>). When required, the install handler is dynamically
+ implements     <tt>IInstallHandler</tt>). When required, the install handler
-   loaded by the installation and update code, and is called at specific points
+ is dynamically     loaded by the installation and update code, and is called
-   during its processing. The install handler code has visibility to classes
+ at specific points    during its processing. The install handler code has
-   from the installation and update support plug-in, and its prerequisite
+ visibility to classes    from the installation and update support plug-in,
- plug-ins.
+ and its prerequisite  plug-ins.
  <p><b>Implementation Note:</b> the detailed list of visible prerequisite
  plug-ins is still evolving. It is expected to include <tt>org.eclipse.core.boot
  </tt> and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt>
-Line 988
+Line 1015
  a functional    description)]: </p>
  <ul>
-       <li> install-initiated - the install handler is called after a feature
+           <li> install-initiated - the install handler is called after a
-   was selected for installation, but before any files were downloaded. It
+ feature     was selected for installation, but before any files were downloaded.
- is  intended  to implement any custom click-through or user registration
+ It   is  intended  to implement any custom click-through or user registration
  dialogs.  The base implementation of this method supplied with the abstract
  class     <tt>BaseInstallHandler       </tt>performs the default click-through
  processing using the license  text supplied as part of the feature manifest.
  On return this method indicates  success (installation continues) of failure
  (installation is aborted).</li>
-        <li> install-downloaded - the install handler is called after all
+            <li> install-downloaded - the install handler is called after
- the   required  feature files were downloaded (feature, plugins, data) but
+ all   the   required  feature files were downloaded (feature, plugins, data)
- before   the actual  installation is performed. The install handler is expected
+ but   before   the actual  installation is performed. The install handler
- to   perform verification  of the non-plug-in data files (eg. security),
+ is expected   to   perform verification  of the non-plug-in data files (eg.
- or any   other pre-install processing.&nbsp; On return this method indicates
+ security),  or any   other pre-install processing.&nbsp; On return this method
- success   (installation continues) or failure (installation is aborted).</li>
+ indicates   success   (installation continues) or failure (installation is
-        <li> install-completion - the install handler is called after the
+ aborted).</li>
- feature   information and the plug-ins were installed. It is expected to
+            <li> install-completion - the install handler is called after
- complete the  installation of any non-plug-in data that was part of the feature.
+ the   feature   information and the plug-ins were installed. It is expected
- On return  this method indicates success (returns custom install log) or
+ to  complete the  installation of any non-plug-in data that was part of the
- failure (installation  is aborted). On failure, the install handler is expected
+ feature.  On return  this method indicates success (returns custom install
- to perform any required cleanup.</li>
+ log) or failure (installation  is aborted). On failure, the install handler
-        <li> uninstall-initiated - the install handler is called when a feature
+ is expected to perform any required cleanup.</li>
-   is selected for removal, but before any of the standard uninstall processing
+            <li> uninstall-initiated - the install handler is called when
-   has taken place. It is passed the custom install log created by the install
+ a  feature    is selected for removal, but before any of the standard uninstall
-   handler install-completion step.</li>
+  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 completion
    of the standard uninstall steps. It is passed the custom install log created
    by the install handler install-completion step.</li>
-Line 1026
+Line 1054
  <p>Features are verified as follows: </p>
  <ul>
-       <li> download and verify the feature archive (use base Java jar verification)</li>
+           <li> download and verify the feature archive (use base Java jar
+ verification)</li>
         <li> for each plug-in archive</li>
    <ul>
        <li> verify the archive jar content (use base Java jar verification)</li>
-        <li> verify plug-in id and version from <tt>&lt;plugin&gt;</tt> entry
+            <li> verify plug-in id and version from <tt>&lt;plugin&gt;</tt>
-   in feature manifest matches downloaded plugin.xml</li>
+  entry    in feature manifest matches downloaded plugin.xml</li>
    </ul>
         <li> for each non-plugin file</li>
-Line 1044
+Line 1073
  </ul>
        In general, when processing signed jars, the user will be prompted
- for   each unrecognized certificate. The response choices will include aborting
+   for   each unrecognized certificate. The response choices will include
-   the installation (originator is not trusted), continuing the installation
+ aborting     the installation (originator is not trusted), continuing the
-   (originator is trusted for this installation).
+ installation     (originator is trusted for this installation).
  <h2> <a name="Update_Server"></a> Update Server</h2>
-       The default Eclipse update server is any URL-accessible server. The
+           The default Eclipse update server is any URL-accessible server.
- default   implementation assumes a fixed-layout server. The content of the
+ The   default   implementation assumes a fixed-layout server. The content
- server (in terms of available features and plug-ins) is described in a site
+ of the   server (in terms of available features and plug-ins) is described
- map file, <i>site.xml</i>. This file can be manually maintained, or can be
+ in a site   map file, <i>site.xml</i>. This file can be manually maintained,
- dynamically   computed by the server.
+ or can be  dynamically   computed by the server.
  <h3> <a name="Site_Map"></a> Site Map</h3>
-       The update server URL can be specified as a full URL to the site map
+           The update server URL can be specified as a full URL to the site
-  file,   or a URL of a directory path containing the site map file (similar
+  map   file,   or a URL of a directory path containing the site map file
-  to index.html   processing). The site map site.xml format is defined by
+ (similar    to index.html   processing). The site map site.xml format is
- the  following dtd:
+ defined by  the  following dtd:
  <p><tt>&lt;?xml encoding="ISO-8859-1"?&gt;</tt> </p>
  <p><tt>&lt;!ELEMENT site (description?, feature*, archive*, category-def*)&gt;</tt>
-Line 1081
+Line 1110
     CDATA #IMPLIED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     CDATA #IMPLIED</tt> <br>
-      <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
+          <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-   #IMPLIED</tt> <br>
+  CDATA    #IMPLIED</tt> <br>
       <tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     CDATA #REQUIRED<br>
      &nbsp;&nbsp;&nbsp; label &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; CDATA
-Line 1127
+Line 1156
        <li> &lt;site&gt; - defines the site map</li>
    <ul>
-       <li> type - optional site type specification. The value refers to a
+           <li> type - optional site type specification. The value refers
- type   string registered via the <a href="#Framework">install framework</a>
+ 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 (used
+            <li> url - optional URL defining the update site baseline URL
-  to  determine individual &lt;feature&gt; and &lt;archive&gt; location).&nbsp;
+ (used    to  determine individual &lt;feature&gt; and &lt;archive&gt; location).&nbsp;
-   Can be relative or absolute. If relative, is relative to site.xml. If not
+     Can be relative or absolute. If relative, is relative to site.xml. If
-   specified, the default is the URL location of the site.xml file.</li>
+ not    specified, the default is the URL location of the site.xml file.</li>
    </ul>
         <li> &lt;description&gt; - brief description as simple text. Intended
    to be translated.</li>
    <ul>
-       <li> url - optional URL for the full description as HTML. The URL can
+           <li> url - optional URL for the full description as HTML. The URL
-  be  specified as absolute of relative. If relative, If relative, is relative
+  can   be  specified as absolute of relative. If relative, If relative, is
-  to site.xml.</li>
+  relative   to site.xml.</li>
         <br>
-      Note, that for NL handling the URL value should be separated to allow
+          Note, that for NL handling the URL value should be separated to
-  alternate  URLs to be specified for each national language.
+ allow    alternate  URLs to be specified for each national language.
    </ul>
         <li> &lt;feature&gt; - identifies referenced feature archive</li>
    <ul>
-       <li> type - optional feature type specification. The value refers to
+           <li> type - optional feature type specification. The value refers
-  a  type  string registered via the <a href="#Framework">install framework</a>
+  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
    feature type for the site. If the site type is the default Eclipse site
  type,  the default feature type is the packaged feature type (as specified
  in this  document).</li>
-        <li> id - optional feature identifier. The information is used as
+            <li> id - optional feature identifier. The information is used
- a  performance   optimization to speed up searches for features. Must match
+ as  a  performance   optimization to speed up searches for features. Must
- the identifier   specified in the feature.xml of the referenced archive (the
+ match  the identifier   specified in the feature.xml of the referenced archive
- url attribute).   If specified, the version attribute must also be specified.</li>
+  (the  url attribute).   If specified, the version attribute must also be
-        <li> version - optional feature version. The information is used as
+ specified.</li>
-  a  performance  optimization to speed up searches for features. Must match
+            <li> version - optional feature version. The information is used
-  the  version specified in the feature.xml of the referenced archive (the
+  as  a  performance  optimization to speed up searches for features. Must
- url attribute).  If specified, the id attribute must also be specified.</li>
+ match  the  version specified in the feature.xml of the referenced archive
-        <li> url - required URL reference to the feature archive. Can be relative
+ (the url attribute).  If specified, the id attribute must also be specified.</li>
-   or absolute. If relative, it is relative to the location of the site.xml
+            <li> url - required URL reference to the feature archive. Can
-  file.       <b>Note</b>: the default site implementation allows features
+ be  relative    or absolute. If relative, it is relative to the location
- to be accessed without being explicitly declared using a &lt;feature&gt; entry.
+ of the  site.xml   file.       <b>Note</b>: the default site implementation
- By default, an undeclared features reference is interpreted as "features/&lt;id&gt;_&lt;version&gt;.jar"</li>
+ allows  features  to be accessed without being explicitly declared using a
+ &lt;feature&gt;  entry. By default, an undeclared features reference is interpreted
+ as "features/&lt;id&gt;_&lt;version&gt;.jar"</li>
          <li>label - optional feature label. The value is used for optimization
    when browsing the site from the update manager. Intended to be translated.<br>
         </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 feature should only be installed on one of the specified
-    os systems. If this attribute is "*", the feature can be installed   on
+      os systems. If this attribute is "*", the feature can be installed
-  all systems (portable implementation). This information is used as a hint
+  on   all systems (portable implementation). This information is used as
-  by the installation and update support (user can force installation of feature
+ a hint   by the installation and update support (user can force installation
-  regardless of this setting).</li>
+ 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>
+     list of architecture designators defined by Eclipse (see Javadoc for
-   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
+      <tt>     org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature
-   be installed on one of the specified systems. If this attribute&nbsp;is
+ 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>
-Line 1195
+Line 1226
     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> nl - optional locale specification. A comma-separated list of
+            <li> nl - optional locale specification. A comma-separated list
- locale   designators defined by Java. Indicates this feature should only be
+  of  locale   designators defined by Java. Indicates this feature should
- installed   on a system running with a compatible locale (using Java locale-matching
+ only  be installed   on a system running with a compatible locale (using
-  rules). If this attribute&nbsp;is "*", the feature can be installed on all
+ Java locale-matching    rules). If this attribute&nbsp;is "*", the feature
-  systems (language-neutral implementation). This information is used as a
+ can be installed on all  systems (language-neutral implementation). This
- hint by the installation and update support (user can force installation
+ information is used as a hint by the installation and update support (user
- 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
+            <li>patch - optional specification indicating if this feature
-  patch. Default is "false".&nbsp;</li>
+ is  a   patch. Default is "false".&nbsp;</li>
    </ul>
-        <li> &lt;archive&gt; - identifies referenced "storage" archive (the
+            <li> &lt;archive&gt; - identifies referenced "storage" archive
-  actual  files referenced via the <tt>&lt;plugin&gt;</tt> or <tt>&lt;data&gt;</tt>
+ (the   actual  files referenced via the <tt>&lt;plugin&gt;</tt> or <tt>&lt;data&gt;</tt>
     elements in the feature manifest). The site simply manages archives as
  a  path-to-URL map. The default Eclipse site implementation does not require
-   the &lt;archive&gt; section to be included in the site map (site.xml). Any
+     the &lt;archive&gt; section to be included in the site map (site.xml).
-   archive reference not explicitly defined as part of an &lt;archive&gt; section
+  Any   archive reference not explicitly defined as part of an &lt;archive&gt;
-   is assumed to be mapped to a url in the form "&lt;archivePath&gt;" relative
+  section   is assumed to be mapped to a url in the form "&lt;archivePath&gt;"
-   to the location of the site.xml file.</li>
+  relative   to the location of the site.xml file.</li>
    <ul>
-       <li> path - required archive path identifier. This is a string that
+           <li> path - required archive path identifier. This is a string
- is  determined  by the <a href="#Feature_Archive_Mapping_Id_To_Path">feature</a>
+ that   is  determined  by the <a
-    referencing this archive and is not otherwise interpreted by the site (other
+  href="#Feature_Archive_Mapping_Id_To_Path">feature</a>      referencing
-   than as a lookup token).</li>
+ this archive and is not otherwise interpreted by the site  (other   than
+ 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>
    </ul>
-        <li> &lt;category-def&gt; - an optional definition of a category that
+            <li> &lt;category-def&gt; - an optional definition of a category
-   can be used by installation and update support to hierarchicaly organize
+  that   can be used by installation and update support to hierarchicaly organize
   features</li>
    <ul>
-       <li> name - category name. Is specified as a path of name tokens separated
+           <li> name - category name. Is specified as a path of name tokens
-   by /</li>
+  separated    by /</li>
         <li> label - displayable label. Intended to be translated.</li>
    </ul>
-Line 1243
+Line 1275
    </ul>
  </ul>
-       Note, that in general the feature.xml&nbsp; manifest documents should
+           Note, that in general the feature.xml&nbsp; manifest documents
-  specify  UTF-8 encoding. For example
+ should    specify  UTF-8 encoding. For example
  <p><tt>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</tt> </p>
  <p>Translatable text contained in the site.xml can be separated into site&lt;_locale&gt;.properties
-Line 1267
+Line 1299
       <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plug-in argives&nbsp;&nbsp;&nbsp;
     (eg. org.eclipse.ui_1.0.3.jar)</tt>
  <h3> <a name="Controlling_Access"></a> Controlling Access</h3>
-       The default Eclipse site implementation provides support for http access
+           The default Eclipse site implementation provides support for http
-    with basic user authentication (userid and password).
+  access    with basic user authentication (userid and password).
  <p>Custom access control mechanisms can be added to base Eclipse in one of
 ways: </p>
-Line 1276
+Line 1309
        <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 object
+            <li> by supplying a custom concrete implementation of the site
-   (installed  on the client machine, update server specified <tt>&lt;site
+ object    (installed  on the client machine, update server specified <tt>&lt;site
- type=""&gt;</tt>  ). The custom concrete site implementation, together with
+   type=""&gt;</tt>  ). The custom concrete site implementation, together
- any server-side   logic support the required control mechanisms.</li>
+ with   any server-side   logic support the required control mechanisms.</li>
  </ul>
-       Eclipse provides an example demonstrating an implementation of an access
+           Eclipse provides an example demonstrating an implementation of
-    mechanism based on feature key files.
+ an  access    mechanism based on feature key files.
  <h2> <a name="Eclipse_Install"></a> Eclipse Install</h2>
  <h3> <a name="Default_Install_Layout"></a> Default Install Layout</h3>
-Line 1316
+Line 1349
  <h3> <a name="Unmanaged_Plugins"></a> "Unmanaged" Plug-Ins</h3>
        Eclipse supports a concept of "unmanaged" plug-ins. These are plug-ins
-   that were directly installed into the Eclipse file tree without being part
+     that were directly installed into the Eclipse file tree without being
-   of a feature (eg. developer unzipping plug-in archive directly into the
+ part    of a feature (eg. developer unzipping plug-in archive directly into
- Eclipse  file tree).
+ the  Eclipse  file tree).
  <p>Eclipse runtime recognizes these plugins during startup and loads the
  plug-in information into the runtime registry following the standard plug-in
  binding rules. The update support also recognizes the presence of this new
-Line 1333
+Line 1366
  <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 the Eclipse
+   multiple   features. When installing and uninstalling features using the
- installation   and update support, these relationship are correctly maintained.
+  Eclipse installation   and update support, these relationship are correctly
- Only one   copy of any version of a plug-in is used.
+  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 any
+      creates problems because plug-ins would be removed without regard to
-   sharing relationships. As a result, Eclipse <b>does not allow</b> plug-ins
+ any    sharing relationships. As a result, Eclipse <b>does not allow</b>
-   to be installed using native installers into the shared installation tree.
+ plug-ins    to be installed using native installers into the shared installation
-   Instead, native installers must establish their own installation root directory.
+ tree.    Instead, native installers must establish their own installation
-   The subdirectory structure is the same as defined for base Eclipse. The
+ root directory.    The subdirectory structure is the same as defined for
- private  root directory is logically linked into the shared Eclipse installation
+ base Eclipse. The  private  root directory is logically linked into the shared
-  via  a link file installed by the native installer. The file path for the
+  Eclipse installation   via  a link file installed by the native installer.
-  link  file is <tt>&lt;configRoot&gt;/links/</tt>. The <tt>&lt;configRoot&gt;
+  The file path for the   link  file is <tt>&lt;configRoot&gt;/links/</tt>.
-  </tt>  location is computed by Eclipse relative to the launch <a
+  The <tt>&lt;configRoot&gt;   </tt>  location is computed by Eclipse relative
-  href="#Multiple%20Launch%20Points"> configuration file</a> . By default,
+  to the launch <a href="#Multiple%20Launch%20Points"> configuration file</a>
-   this is the <tt>install/</tt> directory in the shared Eclipse installation
+  . By default,    this is the <tt>install/</tt> directory in the shared Eclipse
-   tree. </p>
+  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>
-   . The file content is in the form of a Java properties file, with the following
+     . The file content is in the form of a Java properties file, with the
-    properties defined: </p>
+ 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
- path  to the installation directory root, specified in local OS format. The
+   path  to the installation directory root, specified in local OS format.
- optional  annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse
+ The  optional  annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse
  update support  should allow the specified location to be used 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 linked
    plug-ins during the platform startup. The native installer is responsible
-   for uninstalling the link when the corresponding directory is removed. Eclipse
+     for uninstalling the link when the corresponding directory is removed.
-   runtime ignores any links that cannot be resolved. <br>
+  Eclipse   runtime ignores any links that cannot be resolved. <br>
       &nbsp; </p>
       <br>
      <br>
     <br>
    <br>
   <br>
+     <br>
  </body>
  </html>

 Legend:



Removed from v.1.13
 


changed lines


 
Added in v.1.14
 Legend:



Removed from v.1.13
 


changed lines


 
Added in v.1.14
-Removed from v.1.13
+Added in v.1.14

help@eclipse.org	ViewVC Help
Powered by ViewVC 1.0.3